Restricted operation of an electronic device

ABSTRACT

An electronic device changes the current user interface of a respective type of user interface from a first user interface to a second user interface. An individual uses their personal device to set up and configure a device for another user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/843,788, entitled “RESTRICTED OPERATION OF AN ELECTRONICDEVICE”, filed May 6, 2019, and U.S. Patent Application Ser. No.62/856,032 entitled “RESTRICTED OPERATION OF AN ELECTRONIC DEVICE”,filed Jun. 1, 2019, the contents of which are hereby incorporated byreference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for a restricted mode of operationfor an electronic device.

BACKGROUND

As computer processing, memory, and display technologies have improved,electronic devices have become capable of providing increasedfunctionality. Reductions in the size of electronic devices such aslaptop computers, tablets, smartphones, and smartwatches provide userswith constant access to electronic devices and the functionality theyprovide.

BRIEF SUMMARY

While increased access can allow greater productivity, entertainment,and communication, there are times when modern electronic devices canmake it challenging for a user to focus on a task that does not requireuse of the electronic device. For example, when a person is attendingschool, studying, working, or reading, the ability to check email,search the internet, receive notifications, or engage in social mediaactivity can divert a person's attention away from the originallyintended task.

Features are described below for controlling the functionality of anelectronic device, where the device operates according to a restrictedmode of operation in which functions that the electronic device isotherwise capable of performing are not immediately available. Therestricted mode can provide limited functionality or information (e.g.,time and date), while restricting other functions, allowing the user tomaintain focus on a current task.

Some techniques for providing a restricted mode of operation for anelectronic device, however, are generally cumbersome and inefficient.For example, some existing techniques use a complex and time-consuminguser interface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. For example, existing techniques for activating,deactivating, exiting, and/or re-entering a restricted mode areinefficient. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for a restricted mode ofoperation for an electronic device. Such methods and interfacesoptionally complement or replace other methods for a restricted mode ofoperation for an electronic device. Such methods and interfaces reducethe cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated computing devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, a method comprises: at anelectronic device with a display device: displaying, via the displaydevice, a first user interface of a respective type of user interface ofthe electronic device, where the first user interface of a respectivetype of user interface includes one or more elements in a firstarrangement; detecting a sequence of one or more inputs corresponding toa request to change the current user interface of a respective type ofuser interface of the electronic device; in response to detecting thesequence of one or more inputs corresponding to the request to changethe current user interface of a respective type of user interface of theelectronic device, displaying, via the display device, a second userinterface of the respective type of user interface as the current userinterface of a respective type of user interface of the electronicdevice, where the second user interface of a respective type of userinterface includes one or more elements that are different from the oneor more elements of the first user interface of a respective type ofuser interface and/or are in a different arrangement than the firstarrangement of the one or more elements of the first user interface of arespective type of user interface; after changing the current userinterface of a respective type of user interface of the electronicdevice to the second user interface of a respective type of userinterface, detecting the occurrence of a condition that corresponds to atrigger for displaying the current user interface of a respective typeof user interface of the electronic device; and in response to detectingthe occurrence of a condition that corresponds to a trigger fordisplaying the current user interface of a respective type of userinterface of the electronic device: in accordance with a determinationthat a current time corresponds to a predefined time range, displaying,via the display device, a third user interface of a respective type ofuser interface different from the first user interface of a respectivetype of user interface and the second user interface of a respectivetype of user interface, where the third user interface of a respectivetype of user interface includes a predefined set of elements differentfrom the one or more elements of the first user interface of arespective type of user interface and the one or more elements of thesecond user interface of a respective type of user interface, and wherethe predefined set of elements cannot be changed in response to inputdetected at the electronic device; and in accordance with adetermination that a current time does not correspond to the predefinedtime range, displaying the second user interface of a respective type ofuser interface.

In accordance with some embodiments, a non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display device,the one or more programs including instructions for: displaying, via thedisplay device, a first user interface of a respective type of userinterface of the electronic device, where the first user interface of arespective type of user interface includes one or more elements in afirst arrangement; detecting a sequence of one or more inputscorresponding to a request to change the current user interface of arespective type of user interface of the electronic device; in responseto detecting the sequence of one or more inputs corresponding to therequest to change the current user interface of a respective type ofuser interface of the electronic device, displaying, via the displaydevice, a second user interface of the respective type of user interfaceas the current user interface of a respective type of user interface ofthe electronic device, where the second user interface of a respectivetype of user interface includes one or more elements that are differentfrom the one or more elements of the first user interface of arespective type of user interface and/or are in a different arrangementthan the first arrangement of the one or more elements of the first userinterface of a respective type of user interface; after changing thecurrent user interface of a respective type of user interface of theelectronic device to the second user interface of a respective type ofuser interface, detecting the occurrence of a condition that correspondsto a trigger for displaying the current user interface of a respectivetype of user interface of the electronic device; and in response todetecting the occurrence of a condition that corresponds to a triggerfor displaying the current user interface of a respective type of userinterface of the electronic device: in accordance with a determinationthat a current time corresponds to a predefined time range, displaying,via the display device, a third user interface of a respective type ofuser interface different from the first user interface of a respectivetype of user interface and the second user interface of a respectivetype of user interface, where the third user interface of a respectivetype of user interface includes a predefined set of elements differentfrom the one or more elements of the first user interface of arespective type of user interface and the one or more elements of thesecond user interface of a respective type of user interface, and wherethe predefined set of elements cannot be changed in response to inputdetected at the electronic device; and in accordance with adetermination that a current time does not correspond to the predefinedtime range, displaying the second user interface of a respective type ofuser interface.

In accordance with some embodiments, a transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display device,the one or more programs including instructions for: displaying, via thedisplay device, a first user interface of a respective type of userinterface of the electronic device, where the first user interface of arespective type of user interface includes one or more elements in afirst arrangement; detecting a sequence of one or more inputscorresponding to a request to change the current user interface of arespective type of user interface of the electronic device; in responseto detecting the sequence of one or more inputs corresponding to therequest to change the current user interface of a respective type ofuser interface of the electronic device, displaying, via the displaydevice, a second user interface of the respective type of user interfaceas the current user interface of a respective type of user interface ofthe electronic device, where the second user interface of a respectivetype of user interface includes one or more elements that are differentfrom the one or more elements of the first user interface of arespective type of user interface and/or are in a different arrangementthan the first arrangement of the one or more elements of the first userinterface of a respective type of user interface; after changing thecurrent user interface of a respective type of user interface of theelectronic device to the second user interface of a respective type ofuser interface, detecting the occurrence of a condition that correspondsto a trigger for displaying the current user interface of a respectivetype of user interface of the electronic device; and in response todetecting the occurrence of a condition that corresponds to a triggerfor displaying the current user interface of a respective type of userinterface of the electronic device: in accordance with a determinationthat a current time corresponds to a predefined time range, displaying,via the display device, a third user interface of a respective type ofuser interface different from the first user interface of a respectivetype of user interface and the second user interface of a respectivetype of user interface, where the third user interface of a respectivetype of user interface includes a predefined set of elements differentfrom the one or more elements of the first user interface of arespective type of user interface and the one or more elements of thesecond user interface of a respective type of user interface, and wherethe predefined set of elements cannot be changed in response to inputdetected at the electronic device; and in accordance with adetermination that a current time does not correspond to the predefinedtime range, displaying the second user interface of a respective type ofuser interface.

In accordance with some embodiments, an electronic device comprises: adisplay device; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: displaying, via thedisplay device, a first user interface of a respective type of userinterface of the electronic device, where the first user interface of arespective type of user interface includes one or more elements in afirst arrangement; detecting a sequence of one or more inputscorresponding to a request to change the current user interface of arespective type of user interface of the electronic device; in responseto detecting the sequence of one or more inputs corresponding to therequest to change the current user interface of a respective type ofuser interface of the electronic device, displaying, via the displaydevice, a second user interface of the respective type of user interfaceas the current user interface of a respective type of user interface ofthe electronic device, where the second user interface of a respectivetype of user interface includes one or more elements that are differentfrom the one or more elements of the first user interface of arespective type of user interface and/or are in a different arrangementthan the first arrangement of the one or more elements of the first userinterface of a respective type of user interface; after changing thecurrent user interface of a respective type of user interface of theelectronic device to the second user interface of a respective type ofuser interface, detecting the occurrence of a condition that correspondsto a trigger for displaying the current user interface of a respectivetype of user interface of the electronic device; and in response todetecting the occurrence of a condition that corresponds to a triggerfor displaying the current user interface of a respective type of userinterface of the electronic device: in accordance with a determinationthat a current time corresponds to a predefined time range, displaying,via the display device, a third user interface of a respective type ofuser interface different from the first user interface of a respectivetype of user interface and the second user interface of a respectivetype of user interface, where the third user interface of a respectivetype of user interface includes a predefined set of elements differentfrom the one or more elements of the first user interface of arespective type of user interface and the one or more elements of thesecond user interface of a respective type of user interface, and wherethe predefined set of elements cannot be changed in response to inputdetected at the electronic device; and in accordance with adetermination that a current time does not correspond to the predefinedtime range, displaying the second user interface of a respective type ofuser interface.

In accordance with some embodiments, an electronic device comprises: adisplay device; means for displaying, via the display device, a firstuser interface of a respective type of user interface of the electronicdevice, where the first user interface of a respective type of userinterface includes one or more elements in a first arrangement; meansfor detecting a sequence of one or more inputs corresponding to arequest to change the current user interface of a respective type ofuser interface of the electronic device; means for, in response todetecting the sequence of one or more inputs corresponding to therequest to change the current user interface of a respective type ofuser interface of the electronic device, displaying, via the displaydevice, a second user interface of the respective type of user interfaceas the current user interface of a respective type of user interface ofthe electronic device, where the second user interface of a respectivetype of user interface includes one or more elements that are differentfrom the one or more elements of the first user interface of arespective type of user interface and/or are in a different arrangementthan the first arrangement of the one or more elements of the first userinterface of a respective type of user interface; and means for, afterchanging the current user interface of a respective type of userinterface of the electronic device to the second user interface of arespective type of user interface, detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice; means for, in response to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current timecorresponds to a predefined time range, displaying, via the displaydevice, a third user interface of a respective type of user interfacedifferent from the first user interface of a respective type of userinterface and the second user interface of a respective type of userinterface, where the third user interface of a respective type of userinterface includes a predefined set of elements different from the oneor more elements of the first user interface of a respective type ofuser interface and the one or more elements of the second user interfaceof a respective type of user interface, and where the predefined set ofelements cannot be changed in response to input detected at theelectronic device; and in accordance with a determination that a currenttime does not correspond to the predefined time range, displaying thesecond user interface of a respective type of user interface.

In accordance with some embodiments, a method comprises: at anelectronic device with a display device: operating the electronic devicein a first mode; and while operating the electronic device in the firstmode: displaying, via the display device, a user interface of arespective type of user interface; detecting a first sequence of one ormore inputs corresponding to a request to exit the first mode, the firstsequence of one or more inputs including at least one input that isdetected while displaying the user interface of a respective type ofuser interface; and after detecting at least one of the inputs in thefirst sequence of one or more inputs and prior to ceasing to operate theelectronic device in the first mode, presenting an alert indicating thatinformation indicating that the electronic device has exited the firstmode will be reported to another user; after presenting the alert,detecting a second sequence of one or more inputs; and in response todetecting the second sequence of one or more inputs and in accordancewith a determination that the second sequence of one or more inputscorresponds to a request to exit the first mode, ceasing to operate theelectronic device in the first mode.

In accordance with some embodiments, a non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display device,the one or more programs including instructions for: operating theelectronic device in a first mode; and while operating the electronicdevice in the first mode: displaying, via the display device, a userinterface of a respective type of user interface; detecting a firstsequence of one or more inputs corresponding to a request to exit thefirst mode, the first sequence of one or more inputs including at leastone input that is detected while displaying the user interface of arespective type of user interface; and after detecting at least one ofthe inputs in the first sequence of one or more inputs and prior toceasing to operate the electronic device in the first mode, presentingan alert indicating that information indicating that the electronicdevice has exited the first mode will be reported to another user; afterpresenting the alert, detecting a second sequence of one or more inputs;and in response to detecting the second sequence of one or more inputsand in accordance with a determination that the second sequence of oneor more inputs corresponds to a request to exit the first mode, ceasingto operate the electronic device in the first mode.

In accordance with some embodiments, a transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display device,the one or more programs including instructions for: operating theelectronic device in a first mode; and while operating the electronicdevice in the first mode: displaying, via the display device, a userinterface of a respective type of user interface; detecting a firstsequence of one or more inputs corresponding to a request to exit thefirst mode, the first sequence of one or more inputs including at leastone input that is detected while displaying the user interface of arespective type of user interface; and after detecting at least one ofthe inputs in the first sequence of one or more inputs and prior toceasing to operate the electronic device in the first mode, presentingan alert indicating that information indicating that the electronicdevice has exited the first mode will be reported to another user; afterpresenting the alert, detecting a second sequence of one or more inputs;and in response to detecting the second sequence of one or more inputsand in accordance with a determination that the second sequence of oneor more inputs corresponds to a request to exit the first mode, ceasingto operate the electronic device in the first mode.

In accordance with some embodiments, an electronic device comprises: adisplay device; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: operating theelectronic device in a first mode; and while operating the electronicdevice in the first mode: displaying, via the display device, a userinterface of a respective type of user interface; detecting a firstsequence of one or more inputs corresponding to a request to exit thefirst mode, the first sequence of one or more inputs including at leastone input that is detected while displaying the user interface of arespective type of user interface; and after detecting at least one ofthe inputs in the first sequence of one or more inputs and prior toceasing to operate the electronic device in the first mode, presentingan alert indicating that information indicating that the electronicdevice has exited the first mode will be reported to another user; afterpresenting the alert, detecting a second sequence of one or more inputs;and in response to detecting the second sequence of one or more inputsand in accordance with a determination that the second sequence of oneor more inputs corresponds to a request to exit the first mode, ceasingto operate the electronic device in the first mode.

In accordance with some embodiments, an electronic device comprises: adisplay device; means for operating the electronic device in a firstmode; and means for, while operating the electronic device in the firstmode: displaying, via the display device, a user interface of arespective type of user interface; detecting a first sequence of one ormore inputs corresponding to a request to exit the first mode, the firstsequence of one or more inputs including at least one input that isdetected while displaying the user interface of a respective type ofuser interface; and after detecting at least one of the inputs in thefirst sequence of one or more inputs and prior to ceasing to operate theelectronic device in the first mode, presenting an alert indicating thatinformation indicating that the electronic device has exited the firstmode will be reported to another user; after presenting the alert,detecting a second sequence of one or more inputs; and in response todetecting the second sequence of one or more inputs and in accordancewith a determination that the second sequence of one or more inputscorresponds to a request to exit the first mode, ceasing to operate theelectronic device in the first mode.

In accordance with some embodiments, a method includes, at a firstdevice with a display device: displaying, via the display device, asetup user interface of a setup process for setting up a second device;while displaying, via the display device, the setup user interface,detecting a first user input selecting a respective account to beassociated with the second device and while the first device isassociated with a first account; and after the respective account hasbeen selected to be associated with the second device and during thesetup process, displaying, via the display device, a setup userinterface for configuring a respective function of the second device,including: in accordance with a determination that the first account wasselected to be associated with the second device, displaying, via thedisplay device, one or more selectable options associated withconfiguring the respective function of the second device withoutexplicitly identifying a user account associated with the second device;and in accordance with a determination that a second account, differentfrom the first account, was selected to be associated with the seconddevice, displaying, via the display device, the one or more selectableoptions associated with configuring the respective function of thesecond device concurrently with an identifier that explicitly identifiesthe second account.

In accordance with some embodiments, a non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of a first device with a display device, the oneor more programs including instructions for: displaying, via the displaydevice, a setup user interface of a setup process for setting up asecond device; while displaying, via the display device, the setup userinterface, detecting a first user input selecting a respective accountto be associated with the second device and while the first device isassociated with a first account; and after the respective account hasbeen selected to be associated with the second device and during thesetup process, displaying, via the display device, a setup userinterface for configuring a respective function of the second device,including: in accordance with a determination that the first account wasselected to be associated with the second device, displaying, via thedisplay device, one or more selectable options associated withconfiguring the respective function of the second device withoutexplicitly identifying a user account associated with the second device;and in accordance with a determination that a second account, differentfrom the first account, was selected to be associated with the seconddevice, displaying, via the display device, the one or more selectableoptions associated with configuring the respective function of thesecond device concurrently with an identifier that explicitly identifiesthe second account.

In accordance with some embodiments, a transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of a first device with a display device, the oneor more programs including instructions for: displaying, via the displaydevice, a setup user interface of a setup process for setting up asecond device; while displaying, via the display device, the setup userinterface, detecting a first user input selecting a respective accountto be associated with the second device and while the first device isassociated with a first account; and after the respective account hasbeen selected to be associated with the second device and during thesetup process, displaying, via the display device, a setup userinterface for configuring a respective function of the second device,including: in accordance with a determination that the first account wasselected to be associated with the second device, displaying, via thedisplay device, one or more selectable options associated withconfiguring the respective function of the second device withoutexplicitly identifying a user account associated with the second device;and in accordance with a determination that a second account, differentfrom the first account, was selected to be associated with the seconddevice, displaying, via the display device, the one or more selectableoptions associated with configuring the respective function of thesecond device concurrently with an identifier that explicitly identifiesthe second account.

In accordance with some embodiments, a first device includes a displaydevice; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the display device,a setup user interface of a setup process for setting up a seconddevice; while displaying, via the display device, the setup userinterface, detecting a first user input selecting a respective accountto be associated with the second device and while the first device isassociated with a first account; and after the respective account hasbeen selected to be associated with the second device and during thesetup process, displaying, via the display device, a setup userinterface for configuring a respective function of the second device,including: in accordance with a determination that the first account wasselected to be associated with the second device, displaying, via thedisplay device, one or more selectable options associated withconfiguring the respective function of the second device withoutexplicitly identifying a user account associated with the second device;and in accordance with a determination that a second account, differentfrom the first account, was selected to be associated with the seconddevice, displaying, via the display device, the one or more selectableoptions associated with configuring the respective function of thesecond device concurrently with an identifier that explicitly identifiesthe second account.

In accordance with some embodiments, a first device includes a displaydevice; means for displaying, via the display device, a setup userinterface of a setup process for setting up a second device; means for,while displaying, via the display device, the setup user interface,detecting a first user input selecting a respective account to beassociated with the second device and while the first device isassociated with a first account; and means for, after the respectiveaccount has been selected to be associated with the second device andduring the setup process, displaying, via the display device, a setupuser interface for configuring a respective function of the seconddevice, including: in accordance with a determination that the firstaccount was selected to be associated with the second device,displaying, via the display device, one or more selectable optionsassociated with configuring the respective function of the second devicewithout explicitly identifying a user account associated with the seconddevice; and in accordance with a determination that a second account,different from the first account, was selected to be associated with thesecond device, displaying, via the display device, the one or moreselectable options associated with configuring the respective functionof the second device concurrently with an identifier that explicitlyidentifies the second account.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for providing a restricted mode of operation for anelectronic device, thereby increasing the effectiveness, efficiency, anduser satisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for providing a restricted mode ofoperation for an electronic device.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6AC illustrate exemplary user interfaces for operating anelectronic device in accordance with some embodiments.

FIG. 7 illustrates an exemplary method in accordance with someembodiments.

FIG. 8 illustrates an exemplary method in accordance with someembodiments.

FIGS. 9A-9AI illustrate exemplary user interfaces for configuring asecond electronic device, in accordance with some embodiments.

FIG. 10 illustrates an exemplary method for configuring a secondelectronic device, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for a restricted mode of operation for an electronicdevice. For example, while in a restricted mode, functions that theelectronic device is otherwise capable of performing are not immediatelyavailable. A time range can be defined during which the electronicdevice (or, optionally, multiple electronic devices associated with acommon account) is scheduled to operate in the restricted mode. Forexample, a parent can set predefined time ranges (e.g., daily schoolschedules) during which the devices used by the parent's children are tooperate in restricted mode. Techniques for activating (e.g., manuallyactivating) the restricted mode at a time when the restricted mode isnot otherwise scheduled are also described. In some embodiments, whilein the restricted mode, a user can initiate a process on the electronicdevice to exit (e.g., unlock, leave, deactivate) the restricted mode (atleast temporarily). Exiting the restricted mode during a predefined timerange can cause a report to be displayed on another device. For example,if a student exits the restricted mode during school hours, anotification will be displayed on a device of the student's parent(e.g., in a report log on the parent's phone).

Such techniques can reduce the cognitive burden on a user who operates adevice in a restricted mode, thereby enhancing productivity. Further,such techniques can reduce processor and battery power otherwise wastedon redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for a restricted mode ofoperation in accordance with some embodiments. FIGS. 6A-6AC illustrateexemplary user interfaces for a restricted mode of operation inaccordance with some embodiments. FIGS. 7-8 are flow diagramsillustrating methods for a restricted mode of operation in accordancewith some embodiments. The user interfaces in FIGS. 6A-6AC are used toillustrate the processes described below, including the processes inFIGS. 7-8. FIGS. 9A-9AI illustrate exemplary user interfaces forconfiguring a second device, in accordance with some embodiments. FIG.10 is a flow diagram illustrating methods for configuring a seconddevice, in accordance with some embodiments. The user interfaces inFIGS. 9A-9AI are used to illustrate the processes described below,including the processes in FIG. 10.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. paatent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) containsinformation (e.g., values) that relates to the distance of objects in ascene from a viewpoint (e.g., a camera, an optical sensor, a depthcamera sensor). In one embodiment of a depth map, each depth pixeldefines the position in the viewpoint's Z-axis where its correspondingtwo-dimensional pixel is located. In some embodiments, a depth map iscomposed of pixels wherein each pixel is defined by a value (e.g.,0-255). For example, the “0” value represents pixels that are located atthe most distant place in a “three dimensional” scene and the “255”value represents pixels that are located closest to a viewpoint (e.g., acamera, an optical sensor, a depth camera sensor) in the “threedimensional” scene. In other embodiments, a depth map represents thedistance between an object in a scene and the plane of the viewpoint. Insome embodiments, the depth map includes information about the relativedepth of various features of an object of interest in view of the depthcamera (e.g., the relative depth of eyes, nose, mouth, ears of a user'sface). In some embodiments, the depth map includes information thatenables the device to determine contours of the object of interest in az direction.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700-800and 1000 (FIGS. 7-8 and 10). A computer-readable storage medium can beany medium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITD”) in FIG. 5H. The gesture performed with contact 562 is detected ontouch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT′D”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6AC illustrate exemplary user interfaces for a restricted modeof operation, in accordance with some embodiments. The user interfacesin these figures are used to illustrate the processes described below,including the processes in FIGS. 7-8.

FIG. 6A depicts device 600. Device 600 is configured to operateaccording to a restricted mode (described in greater detail below) andone or more modes other than the restricted mode. In some embodiments,device 600 is device 100, 300, or 500. Device 600 has a display device602 depicted as a touch-sensitive display (e.g., touchscreen 504).Touch-sensitive display 602 is configured to detect the intensity ofcontacts. Exemplary components for detecting the intensity of contacts,as well as techniques for their detection, are described in greaterdetail above. Device 600 has a depressible and rotatable input device603 configured to rotate relative to a frame or housing of device 600.Depressible and rotatable input device 603 is configured to rotate aboutan axis that is parallel to the surface of touch-sensitive display 602.

Device 600 is illustrated as a watch (e.g., a smartwatch). As such, someuser interfaces illustrated as being displayed by device 600 arereferred to as a “clock face” or a “watch face.” References to a “clockface” as described herein are not in any way limited to a traditionalnotion of a “clock face,” e.g., a circular display with hour indicationsand one or more hands to indicate time, or a representation of a digitalclock. Any user interface with an indication of time described hereinmay properly be termed a clock face. Relatedly, a “complication” refersto any clock face feature other than those used to indicate the hoursand minutes of a time (e.g., clock hands or hour/minute indications). Insome embodiments, complications provide different types of informationto a user, such as data obtained from an application. In someembodiments, the information conveyed to a user by a complication iscustomizable.

Although device 600 is described with reference to a watch, thetechniques described below are not limited to clocks, watches, clockfaces, and watch faces. The methods and user interfaces described hereincan be applied to other devices and interfaces, including, but notlimited to, desktop computers, laptop computers, tablet computers,smartphones, or the like.

FIGS. 6A-6C illustrate techniques for selecting a user interface of arespective type of user interface. In FIGS. 6A-6C, device 600 is notoperating according to a restricted mode (e.g., a mode in which a firstset of one or more functions available in an unrestricted mode is notavailable while in the restricted mode, and in which a second set of oneor more functions available in an unrestricted mode is available whilein the restricted mode). In some embodiments, the ability to select auser interface of a respective type as described with respect to FIGS.6A-6C is restricted (e.g., not available) while device 600 is operatingaccording to the restricted mode.

In FIGS. 6A-6C, the respective type of user interface is a clock face.However, the techniques described with reference to FIGS. 6A-6C can beapplied to other types of user interfaces. Numerous individual clockfaces are possible using the techniques described here. A user may wishto select a particular clock face (e.g., from a saved library of clockfaces), depending on a particular context. For example, a user may wishto display a particular clock face during working hours to project aprofessional appearance, but change the clock face during the weekend toreflect an interest (such as astronomy, exercise, or photography).

In FIG. 6A, device 600 displays clock face 604. Clock face 604 includesanalog indication of time 604-1, complication 604-2 corresponding to ahealth application, and complication 604-3 corresponding to a musicapplication.

In this example, the user wishes to switch from clock face 604 to adifferent clock face. The user contacts the touch-sensitive display ofdevice 600 with input 610 a (e.g., a tap). In response to adetermination that input 610 a has a characteristic intensity above anintensity threshold, device 600 enters a clock face selection mode,shown on user interface 606 in FIG. 6B. Clock face selection mode allowsthe user to select a clock face. Device 600 indicates that the user hasentered clock face selection mode by visually distinguishing the clockface. User interface 606 visually distinguishes that device 600 hasentered clock face selection mode by centering reduced size clock face606-1 on the display (reduced size clock face 606-1 is based on clockface 604). This indicates to the user that device 600 is in clock faceselection mode while giving the user an indication of what the clockface will look like when displayed at full size.

In some embodiments, user interface 606 includes partial views of asecond clock face 606-2 and a third clock face 606-3. In someembodiments, when device 600 is in clock face selection mode, device 600displays a partial view of another clock face, or clock face option,particularly the clock face or clock face option next in a sequence(e.g., of two or more clock faces available for selection in clock faceselection mode). This further helps the user understand that additionaloptions are available. In some embodiments, only one clock face isdisplayed at any time.

In some embodiments, user interface 606 includes paging dots thatindicate where the user is within a sequence of available clock faces,as well as how many options are available in the sequence. In clock faceselection mode, paging dots may indicate the currently selected clockface, where this clock face falls within a sequence of clock faces, andthe total number of clock faces in the sequence. A paging affordance maybe advantageous in clock face selection mode to help the user navigatethe interface and explore all of the clock face options available.

Clock face selection mode can be used to select a clock face fordisplay, or to select a clock face for editing. In some embodiments,when a clock face such as clock face 606-1 is centered on the display, auser can contact “Customize” affordance 606-4 on touch-sensitive display602 to select the centered clock face for editing and enter into clockface editing mode (as described below in reference to FIGS. 6E-6G).Coupling clock face edit and selection modes in a single interface canallow the user to select different clock faces and edit them quickly andeasily.

A user can select a different clock face (for editing or for display) byproviding an input on touch-sensitive display 602. Device 600 detectsinput 610 b (e.g., a swipe) on the touch-sensitive display. In responseto detecting input 610 b, device 600 updates (e.g., scrolls) userinterface 606, as shown in FIG. 6C. User interface 606, as updated,includes second clock face 606-2 centered on the display. In someembodiments, user interface 606, as updated, includes a partial view ofclock face 606-1.

To select clock face 606-2, the user contacts touch-sensitive display602 on clock face 606-2 (e.g., touch input 610 c). In response todetecting input 610 c (e.g., a tap), device 600 exits the clock faceselection mode and displays full-sized clock face 608 (as shown in FIG.6D), which is based on clock face 606-2. Clock face 608 includes digitalindication of time 608-1 and five complications 608-2 to 608-6.Complication 608-2 corresponds to a calendar application and displaysdate information from the calendar application; complication 608-3corresponds to a calendar application (e.g., the same calendarapplication associated with complication 608-2) and displays calendarevent data from the calendar application; complication 608-4 correspondsto a weather application and displays forecast data from the weatherapplication; complication 608-5 corresponds to a weather application(e.g., the same weather application associated with complication 608-4)and displays current temperature data from the weather application; andcomplication 608-6 corresponds to a messaging application and displays agraphical element (e.g., icon) associated with the messagingapplication. In some embodiments, the graphical element associated withthe messaging application displays data from the messaging application(e.g., a number of new, unread, or missed messages).

Optionally, device 600 provides other methods for selecting a clock facein addition to or in place of the technique described above. In someembodiments, device 600 switches directly from clock face 604 to clockface 608 without entering the clock face selection mode (e.g., withoutdisplaying user interface 606). For example, in response to detecting aswipe gesture from right to left on touch-sensitive display 602 whiledisplaying clock face 604 in FIG. 6A, device 600 replaces clock face 604with clock face 608 (e.g., device 600 ceases display of clock face 604and displays clock face 608).

Having described various techniques for selecting a user interface of arespective type of user interface (e.g., a clock face), attention is nowdirected to methods of editing a user interface of a respective type ofuser interface (e.g., a clock face). FIGS. 6D-6G illustrate techniquesfor editing a user interface of a respective type of user interface. InFIGS. 6D-6G, device 600 is not operating according to a restricted mode.In some embodiments, the ability to edit a user interface as describedwith respect to FIGS. 6D-6G is restricted (e.g., not available) whiledevice 600 is operating according to the restricted mode.

In FIG. 6D, device 600 displays clock face 608. Clock face 608 includescomplication 608-6 that displays information associated with a messagingapplication. In this example, the user wishes to change an aspect ofclock face 608. Specifically, the user decides to change the applicationassociated with complication 608-6.

The user contacts the touch-sensitive display 602 of device 600 withtouch input 610 d. In response to a determination that input 610 d has acharacteristic intensity above an intensity threshold, device 600 entersa clock face edit mode. In some embodiments, clock face edit mode is thesame as (or integrated with) the clock face selection mode describedabove (e.g., a combined clock face selection/edit mode). Clock face editmode allows the user to edit one or more aspects of a clock face.

In the illustrated embodiments, in response to input 610 d, device 600displays user interface 606 described above. User interface 606 shows areduced size clock face 606-2 based on clock face 608, with reduced sizeindication of time 606-2 a and complications 606-2 b to 606-2 f Thisdisplay indicates to the user that device 600 is in clock face edit mode(or selection mode) while giving the user an indication of what theedited clock face will look like on the display.

The user selects the displayed clock face for editing by contacting“Customize” affordance 606-4 with input 610 e (e.g., a tap). In responseto detecting input 610 e, device 600 displays user interface 612, whichincludes a full-size, editable version of clock face 606-2. Userinterface 612 visually indicates an element of the clock face forediting. As shown on user interface 612, the complication 612-6(corresponding to element 606-2 f and complication 608-6) has beenselected for editing, as indicated by outline 612-7 a and title bar612-7 b. The other elements of the clock face are retained, as shown bydigital indication of time 612-1 and complications 612-2 through 612-5.

In some embodiments, user interface 612 displays paging dots 612-8 thatindicate where the user is within a sequence of options, as well as howmany options are available in the sequence. In clock face edit mode,paging dots may indicate which editable aspect of the clock face a useris editing, where this aspect falls within a sequence of editableaspects, and the total number of editable aspects in the sequence.Paging dots may be advantageous in clock face edit mode to help the usernavigate the interface and explore all of the editable options availablewithin each type of clock face.

In this example, two aspects of the clock face are available for userediting: (1) color scheme and (2) complications. This is depicted bypaging dots 612-8 a and 612-8 b. Editing the color of a clock face caninclude, e.g., changing a color of a clock face background (e.g.,substituting a color if the clock face background is a particular color,or selecting a different image if the clock face background includes animage), changing a color of part or all of a seconds hand (if includedon the clock face), changing a color of an hour and/or minuteindication, and/or changing a color of a number or colon in the displayof a representation of a digital clock.

User interface 612 is for editing complications, the second editableaspect of the clock face. This is relayed to the user by highlightingpaging dot 612-8 b. By viewing paging dots 612-8, the user recognizesthat complications are the second of two editable aspects of this clockface.

The user may move (e.g., rotate) depressible and rotatable input device603 to cycle through different options for editing different aspects ofthe clock face. On user interface 612, the user may select differentoptions (e.g., application data) for complication 612-6 through input610 f (e.g., movement of depressible and rotatable input device 603).Advantageously, using a rotatable input device to cycle through editingoptions (rather than using, e.g., a touch interaction) frees up touchinteractions with the screen to instead provide other functionalities(e.g., selecting which complication to edit), thus expanding theinteractability of the device. Using a rotatable input device is alsohelpful in cases where smaller elements of the display are being edited,as finer-scale touch gestures can be difficult on a reduced-sizedisplay, especially for users with large fingers that can block a user'sview of the screen while editing.

Also displayed on user interface 612 is positional indicator 612-9.Positional indicator 612-9 is an indicator of a current position along aseries of positions. This can be used, for example, in combination withdepressible and rotatable input device 603. On user interface 612,positional indicator 612-9 indicates to the user the position of thecurrently selected option within a series of all selectable options.

In response to detecting input 610 f, device 600 edits complication612-6, in this case by changing the data associated with thecomplication from messaging application data to workout application data(e.g., an affordance for launching a workout application). This is shownby changing the graphical element displayed at complication 612-6, whilestill highlighting complication 612-6 with outline 612-7 a and title bar612-7 b. The other elements of the clock face remain the same.Positional indicator 612-9 has been updated to indicate the position ofthe workout application data in a sequence of data options.

As indicated by paging dot 612-8 b, the complications are the secondeditable aspect of this clock face within a sequence of editableaspects. The user may select a first editable aspect (e.g., color) byswiping on the touch-sensitive display (e.g., swiping from left toright). In response to detecting the swipe, device 600 displays a userinterface for editing the color scheme of the clock face (e.g., byrotating depressible and rotatable input device 603).

While FIGS. 6D-6G illustrate editing of only complication 612-6,multiple complications can be edited. A user can select a particularcomplication for editing by contacting the corresponding position of thecomplication. Outline 612-7 a then transitions from the previouslyselected complication or element to the currently selected complicationor element and depressible and rotatable input device 603 can then beused to edit the complication or element at the selected location. Insome embodiments, an element (e.g., complication) can be selected byswiping the touch-sensitive display, or rotating the depressible androtatable input device.

As described above, the user can scroll through the available optionsusing movement of the depressible and rotatable input device. However, auser may also wish to scroll through the available options using asecond type of input, such as a contact (e.g., a swipe) on thetouch-sensitive display. In some embodiments, a user can swipe thetouch-sensitive display in a different direction than the swipe used forvisually indicating a second element of the clock face for editing(e.g., a downward swipe on the display). For example, to scroll throughthe available options, the user can swipe in a substantially horizontaldirection to scroll through editable aspects (e.g., with swipes movingleft-to-right resulting in scrolling through the sequence of editableaspects in one direction, and swipes moving right-to-left resulting inscrolling through the sequence of editable aspects in a differentdirection). In this example, the user can swipe in a substantiallyvertical direction to scroll through available options (e.g., withswipes moving downwards resulting in scrolling through the sequence ofavailable options in one direction, and swipes moving upwards resultingin scrolling through the sequence of available options in a differentdirection). In some embodiments, the user can swipe the display at ornear the location of the displayed positional indicator to scrollthrough the sequence of available options.

Having finished editing the clock face, the user can now exit clock faceedit mode and display the edited clock face on the display. In responseto input 610 g (e.g., depression of depressible and rotatable inputdevice 603), device 600 exits clock face edit mode and displays editedclock face 614, as depicted in FIG. 6H. Edited clock face 614 is thesame as clock face 608, except for updated complication 614-1. In someembodiments, in response to input 610 g, device 600 returns to userinterface 606 (e.g., exits clock face edit mode and returns to clockface selection mode), which is updated to display a representation ofthe edited clock face, and then displays edited clock face 614 (asdepicted in FIG. 6H) in response to another user input (e.g., depressionof depressible and rotatable input device 603) while displaying userinterface 606.

FIGS. 6A-6H illustrate exemplary embodiments of selecting and editing aclock face, but a number of other potential embodiments are possiblewithin the scope of the techniques described herein, where device 600selects and/or edits a clock face in response to a sequence of one ormore inputs. Clock face edit mode allows the user to alter multipleeditable aspects of the clock faces described herein. In someembodiments, in response to detecting a swipe on the touch-sensitivedisplay, device 600 selects a second element of the clock face forediting, which in response to detecting another user input (e.g., amovement of the depressible and rotatable input device), may be edited.This allows the user to cycle through different editable aspects of thedisplayed clock face, such as colors, number and/or type ofcomplications, and display density.

Turning to FIG. 6I, in some embodiments, a complication can be selectedto launch an application (e.g., make a background or suspendedapplication active). For example, an affordance representing acomplication on a clock face can display a set of information from thecorresponding application. However, a user may wish to view additionalinformation from the application, or launch the full application itself.Complication 614-1 represents a workout application and includes anaffordance for launching the workout application. To launch the workoutapplication, a user contacts the display at complication 614-1 (e.g.,touch 610 h). In response, device 600 launches the workout applicationand begins an Outdoor Walk, as depicted on user interface 616 in FIG.6J. User interface 616 shows the type of workout (Outdoor Walk),distance (0.01 miles), and elapsed time (00:08:52).

In FIGS. 6I-6J, device 600 is not operating according to a restrictedmode. In some embodiments, the ability to launch an application (e.g., aparticular application), access an open application, and/or close anapplication is restricted (e.g., not available) while device 600 isoperating according to the restricted mode.

Turning to FIG. 6K, display 602 becomes inactive (e.g., in response todevice 600 determining that no input has been received for apredetermined amount of time, in response to detecting a predeterminedgesture (e.g., a wrist-down gesture), or in response to detecting aninput (e.g., a sequence of one or more inputs that cause display 602 tobecome inactive)).

While display 602 is inactive, device 600 detects the occurrence of acondition (e.g., a tap, wrist raise, movement of depressible androtatable input device 603, an application closing, or the like) thatcorresponds to a trigger for displaying the current clock face of device600. In response to detecting the occurrence of a condition thatcorresponds to a trigger for displaying the current clock face, device600 displays a clock face, where the clock face that is displayeddepends on whether or not the current time corresponds to a predefinedtime range during which device 600 is to operate in a restricted mode.In some embodiments, the current time corresponds to the predefined timerange if the current time is within the predefined time range. In someembodiments, the predefined time range is absolute (e.g., from a definedstart time (e.g., 9:00 am) to a defined end time (e.g. 3:00 pm) orrelative (e.g., within a defined amount of time (e.g., 1 hour) from whena restricted mode is entered). In some embodiments, the predefined timerange is set by a device remote to device 600 (e.g., by device 650described with reference to FIGS. 6AA-6AC). In some embodiments, thepredefined time range is associated with a user account associated withdevice 600 (e.g., the predefined time range applies to multiple devicesassociated with a user account).

In accordance with a determination that the current time does notcorrespond to the predefined time range, device 600 does not operateaccording to a restricted mode and displays clock face 614 (e.g., thecurrently selected clock face). In some embodiments, rather thandisplaying the currently-selected clock face, device 600 displays themost recently displayed interface (e.g., user interface 616 in theillustrated example). In accordance with a determination that thecurrent time corresponds to the predefined time range, device 600operates according to a restricted mode of operation (e.g., enters oractivates the restricted mode). The predefined time range in theillustrated embodiment is 8:00 am to 3:00 pm. In FIG. 6L, the currenttime is 8:00 am, which corresponds to the predefined time range, sodevice 600 enters the restricted mode.

In some embodiments, operating in the restricted mode includesdisplaying a restricted user interface. FIG. 6L depicts an embodiment ofa restricted user interface, restricted clock face 618. In someembodiments, if clock face 614 (or user interface 616) is displayed whenthe current time reaches the predefined time range, device 600 ceasesdisplay of clock face 614 (or user interface 616) and replaces it withrestricted clock face 618. As described in greater detail below, in someembodiments, inputs on display 602 while displaying restricted clockface 618 do not cause a visible response while in restricted mode, norare notifications provided.

Display of restricted clock face 618 indicates that device 600 isoperating in a restricted mode and includes graphical elements (e.g., apredefined set of elements) that are different from the graphicalelements of other user interfaces (e.g., clock faces 604, 608, and 614)available for display by device 600. In some embodiments, the graphicalelements of restricted clock face 618 cannot be changed (e.g., edited orremoved), and additional graphical element cannot be added to restrictedclock face 618 (e.g., cannot be added without first existing therestricted mode), in response to input detected at device 600.

In the illustrated embodiment, restricted clock face 618 includes analogindication of time 618-1, indication 618-2 of the date, and digitalindication of time 618-3. Element 618-1 a of analog indication of time618-1 corresponds to a current hour of the current time and is visuallyemphasized relative to other elements of analog indication of time 618-1that correspond to hours other than the current hour. Restricted clockface 618 includes an indication 618-4 of a user's name (e.g., full firstand last name, first name only, full first name and last initial,initials only (e.g., first and last initial only)). In some embodiments,the user's name is customizable (e.g., via device 600 or an externaldevice).

In the illustrated embodiment, restricted clock face 618 includes adistinguishing graphical element, in particular, large ring 618-1 b withan outer diameter that is substantially the same as (slightly smallerthan) the horizontal dimension (e.g., width) of display device 602(e.g., the outer diameter of ring 618-1 b is greater than 90% of thewidth of the display). Ring 618-1 b is visually distinguishable in thatit is not an arbitrarily defined area of clock face 618. In someembodiments, ring 618-1 b is a prominent color, such as yellow. In someembodiments, ring 618-1 b is not included in any other clock facesavailable on device 600. For example, none of the faces provided in theclock face selection mode described above in, e.g., FIGS. 6B-6C can bechanged in response to input detected at the electronic device toinclude ring 618-1 b. In some embodiments, the distinguishing graphicalelement is displayed via the display device only while the restrictedclock face is the current clock face (e.g., the element is unique to therestricted clock face). In some embodiments, the distinguishing elementis in a foreground of the restricted clock face (e.g., thedistinguishing element is not a background image). Ring 618-1 b ismerely an example of a distinguishable graphical element—other elementswith the general characteristics of ring 618-1 b described above (e.g.,not available on other clock faces or user interfaces) can bedistinguishing graphical elements.

Restricted clock face 618 includes graphical element 618-5 correspondingto the workout application represented by user interface 616. In someembodiments, device 600 continues to run the workout application afterentering the restricted mode. Device 600 can continue to run the workoutapplication even while operating in the restricted mode so as not tointerrupt an ongoing workout. In some embodiments, device 600 determineswhat operation to perform (e.g., continue to execute in the background,suspend, pause, or close) with respect to an open application uponentering the restricted mode based on the type of application that isrunning. For example, device 600 can suspend or close types ofapplications that can be resumed from a point at which they are stopped(e.g., a user can restart a music track at a point that a musicapplication is paused or stopped), whereas device 600 can continue toexecute types of applications (e.g., a workout application) that oftencannot be easily resumed (e.g., a workout application cannot accuratelytrack the pace of a runner if the application is closed during therunner's workout).

In the illustrated embodiment of FIG. 6L, in accordance with adetermination that an application is open, device 600 displays graphicalelement 618-5 on restricted clock face 618 to indicate that the workoutapplication is open. In some embodiments, device 600 displays agraphical element for an application on restricted clock face 618 if theapplication is open and executing in the background (e.g., a backgroundapplication) but not if the application is suspended or hibernated(e.g., open but not running). In some embodiments, unlike complication614-1 on clock face 614, graphical element 618-5 cannot be selected toaccess (e.g., launch or display) the workout application. For example, atouch input on graphical element 618-5 does not cause the workoutapplication to be displayed, and in some embodiments, does not cause anyfunction to be performed (e.g., device 600 does not perform anyaffirmative operation in response to an input corresponding to selectionof graphical element 618-5). In some embodiments, device 600 does notrespond to any touch inputs on touch-sensitive display 602 (e.g., device600 does not enter a clock face selection or editing mode in response toinput on touch-sensitive display 602 while restricted clock face 618 isdisplayed). In some embodiments, device 600 does not providenotifications (e.g., graphical, haptic, audible) of events (e.g.,incoming phone calls, emails, text messages, alarm) while in therestricted mode (e.g., while displaying restricted clock face 618).

In some embodiments, device 600 suspends or closes applications that areactive when the current time reaches the predefined time range. In somesuch embodiments, in accordance with a determination that theapplication is not running (e.g., is closed or suspended), device 600displays restricted clock face 618 without a graphical elementcorresponding to the workout application.

In some embodiments, the predefined set of graphical elements of therestricted clock face has a predefined configuration or layout that isdifferent from all other available clock faces (e.g., clock faces 604,608, and 614). In some embodiments, restricted clock face 618 is notavailable when device 600 is not in the restricted mode (e.g.,restricted clock face 618 is not available in the clock face selectionmode illustrated in FIGS. 6B-6C). In some embodiments, a user cannotselect the clock face corresponding to the restricted mode. In someembodiments, the restricted clock face is a static system setting.

FIGS. 6M-6O illustrate techniques for exiting the restricted mode (alsoreferred to as “unlocking” the restricted mode) according to someembodiments. Exiting the restricted mode allows device 600 to displayother clock faces (e.g., customizable and/or changeable clock faces,such as clock faces 604, 608, and 614) and to perform operations thatare not available while operating in the restricted mode (e.g., accessapplications). The techniques for exiting the restricted mode describedbelow are unlikely to be performed accidentally and involve a deliberateeffort by the user to exit the restricted mode. In some instances, thedeliberate effort involved may deter a user from deactivating therestricted mode and allow the user to maintain focus on a current task.Furthermore, device 600 is prevented from incidentally exiting therestricted mode while also allowing a user to access the fullfunctionality of the device (e.g., if a particular need or emergencyarises).

In FIG. 6M, device 600 detects input 610 i. In FIG. 6M, input 610 iincludes a depression of depressible and rotatable input device 603. Insome embodiments, input 610 i includes a contact on touch-sensitivedisplay 602 (e.g., a contact with a characteristic intensity that isdetermined to be greater than a threshold intensity) or rotation ofdepressible and rotatable input device 603.

In response to detecting input 610 i, device 600 displays user interface620 illustrated in FIG. 6N. In FIG. 6N, user interface 620 replacesrestricted clock face 618 (e.g., device 600 ceases displaying restrictedclock face 618 and displays user interface 620). In some embodiments,device 600 overlays user interface 620 over a portion of restrictedclock face 618. User interface 620 includes information related to therestricted mode (e.g., information related to exiting the restrictedmode). In the illustrated example, user interface 620 includes title620-1 (“EXIT RESTRICTED MODE”), alert 620-2 (“Leaving appears in therestricted mode report”), and indication 620-3 of the remaining durationof the restricted mode (“Time Left: 6 HRS 55 MIN”). Displaying how muchlonger the restricted mode is scheduled is advantageous in circumstancesin which the user of device 600 did not set the predefined time range(e.g., if a user's parent set the predefined time range, the user maynot otherwise know how long the restricted mode is scheduled to last).

In the illustrated embodiment, alert 620-2 indicates that informationindicating that device 600 has exited the restricted mode (e.g., an exitevent) will be reported to another user. In the illustrated embodiment,exiting the restricted mode on device 600 is reported to device 650illustrated in FIG. 6AA. In some embodiments, exiting the restrictedmode on device 600 is reported to device 650 in accordance with adetermination that device 650 is associated with a user that is toreceive information indicating that device 600 exited the restrictedmode (e.g., device 650 is associated with a user account of the userthat is to receive information indicating that device 600 exited therestricted mode).

In some embodiments, the information indicating that device 600 hasexited the restricted mode is reported to another user directly (e.g.,via Bluetooth or NFC) from device 600 to the device of the receivinguser (e.g., device 650). In some embodiments, the information indicatingthat device 600 has exited the restricted mode is reported to anotheruser via a common network connection (e.g., Wi-Fi, internet, LAN, etc.).

User interface 620 includes affordance 620-4 for cancelling the exitprocess (labeled “DON'T EXIT”). In response to selection of affordance620-4, device 600 remains in the restricted mode, cancels the exitprocess, and returns to restricted clock face 618 (e.g., ceasesdisplaying user interface 620 and displays restricted clock face 618).

User interface 620 includes affordance 620-5 for exiting (unlocking,leaving) the restricted mode (labeled “EXIT”). In the illustratedembodiment, initially, user interface 620 is partially displayed suchthat affordance 620-5 is only partially displayed (e.g., a portion ofuser interface 620 is hidden or not displayed). In some embodiments,affordance 620-5 can be selected while partially displayed. In someembodiments, affordance 620-5 cannot be selection while partiallydisplayed. In some embodiments, affordance 620-5 is completely displayedin response to input 610 i (e.g., when user interface 620 is initiallydisplayed), without further input. In some embodiments, affordance 620-5is completely hidden (e.g., not visible in FIG. 6N) when user interfaceis initially displayed, and a user must provide additional input todisplay affordance 620-5 (e.g., by scrolling user interface 620 asdescribed below).

In response to detecting input 610 j (e.g., rotation of depressible androtatable input device 603, an upward drag gesture on touch-sensitivedisplay 602, a tap gesture on partially displayed affordance 620-5),device 600 scrolls user interface 620, revealing a previously hiddenportion of user interface 620 such that affordance 620-5 is completelydisplayed, as illustrated in FIG. 60. In some embodiments, in responseto detecting input 610 j, device 600 places focus on affordance 620-5.

In response to detecting selection of affordance 620-5 (e.g., detectingtouch input 610 k on affordance 620-5 or depression of depressible androtatable input device 603 while focus is on affordance 620-5), device600 exits the restricted mode and ceases display of user interface 620(and restricted clock face 618, if still displayed).

In some embodiments, in response to detecting input corresponding to arequest to exit the restricted mode (e.g., input 610 k), device 600records data representing an indication that device 600 has ceasedoperating in the restricted mode. In some embodiments, the recorded dataincludes a time at which device 600 ceased operating in the restrictedmode (e.g., in response to detecting input 610 k) and a duration of timefor which device 600 was not operating in the restricted mode (e.g., anamount of time between exiting the restricted mode and re-entering therestricted mode or reaching the end of a predefined time range). Forexample, device 600 records the data for transmission to device 650(e.g., the recorded data is transmitted (directly or indirectly) todevice 650). In some embodiments, device 600 begins to record data uponexiting the restricted mode and, optionally, continues to record datawhile device 600 remains outside of the restricted mode. In someembodiments, the data causes a report of the exit event to be displayedat device 650. In some embodiments, the recorded data is transmittedupon device 600 exiting the restricted mode (e.g., in response todetecting input 610 k). In some embodiments, the recorded data istransmitted upon device 600 re-entering the restricted mode. In someembodiments, the recorded data is transmitted periodically (e.g., fiveminutes, every hour, or at the end of the day or the end of the week).

In the illustrated embodiment, upon exiting the restricted mode, device600 replaces restricted clock face 618 with customizable clock face 614as the current clock face, as shown in FIG. 6P. In some embodiments,device 600 replaces restricted clock face 618 with a user interface thatwas most recently displayed prior to entering the restricted mode (e.g.,user interface 616 of the workout application).

Upon exiting the restricted mode, device 600 operates according to a“normal” mode that includes functionality not accessible in therestricted mode. For example, while displaying clock face 614 in FIG.6P, device 600 receives input 6101 (e.g., depression of depressible androtatable input device 603). In response to detecting input 6101, device600 displays user interface 622 (e.g., an application springboard)including a plurality of affordances for launching correspondingapplications or user interfaces. In contrast to the operation of device600 while in the restricted mode, user interface 622 is not availabledirectly from restricted clock face 618. As illustrated above,depression of depressible and rotatable input device 603 whilerestricted clock face 618 is displayed results in display of userinterface 620. In the illustrated embodiment, device 600 must exit therestricted mode in order to display user interface 622.

In response to detecting selection of affordance 622-1 (e.g., detectingtap input 610m on affordance 622-1), device 600 displays user interface624 (e.g., settings menu). As illustrated in FIG. 6R, user interface 624includes affordances associated with various system features, includingaffordance 624-1 associated with the restricted mode.

In response to detecting selection of affordance 624-1 (e.g., detectingtap gesture input 610 n), device 600 displays user interface 626, whichincludes information related to the restricted mode. User interface 626includes affordance 626-1 (e.g., toggle button), which indicates thestate of the restricted mode and, optionally, can be used for activatingand deactivating the restricted mode under certain conditions. Asillustrated in FIG. 6S, since the current time corresponds to thepredefined time range, affordance 626-1 is deactivated (e.g., cannot beselected), as indicated by being greyed out. In some embodiments, whenthe current time does not correspond to the predefined time range, therestricted mode can be activated by navigating to user interface 626(e.g., via the sequence of interfaces and inputs illustrated in FIGS.6P-6R) and selecting affordance 626-1.

User interface 626 includes a report log 626-2 indicating occurrences ofone or more devices exiting a restricted mode (e.g., exit events).Report log 626-2 includes information concerning exit events associatedwith the restricted mode. Exit event items 626-2 a through 626-2 cindicate a time at which the restricted mode was exited (e.g., the timean exit event began) and a duration of the exit event (e.g., the amountof time that a device remained out of the restricted mode during thepredefined time range). Exit event item 626-2 a corresponds to the exitevent illustrated in FIGS. 6O-6P, which began at 8:05 and has lasted oneminute (since the current time in FIG. 6S is 8:06). In some embodiments,report log 626-2 includes information about exit events from previousdays. For example, exit event items 626-2 b and 626-2 c provideinformation about exit events that occurred during a previous day. Insome embodiments, report log 626-2 organizes exit event items by day. Insome embodiments, report log 626-2 organizes exit event items byrestricted mode period (e.g., multiple restricted mode periods can bescheduled in a day). In some embodiments, device 600 aggregates exitevents from multiple devices (e.g., devices that share a common accountor are associated with a single user). In some embodiments, a predefinedtime range applies to multiple devices and, optionally, exiting therestricted mode on any of the multiple devices during the predefinedtime range results in an exit event that is included in the report log.In some embodiments, an exit event item includes an indication of adevice associated with the corresponding exit event. In someembodiments, report log 626-2 includes exit event items associated onlywith device 600.

In the illustrated embodiment, after exiting the restricted mode, device600 will re-enter the restricted mode (e.g., re-display restricted clockface 618) if certain criteria are met while the current time correspondsto the predefined time range. For example, if an input is not detectedwithin a predetermined amount of time or device 600 detects an inputcorresponding to a request to deactivate display of content (e.g., awrist gesture consistent with a user putting his or her wrist down,indicating that the user is not looking at device 600), device re-entersthe restricted mode. In some embodiments, device 600 displays restrictedclock face 618 at the time of re-entering the restricted mode. In someembodiments, if display 602 is not displaying content at the time thecriteria for re-entering the restricted mode are met, device 600displays restricted clock face 618 upon detecting the occurrence of acondition that corresponds to a trigger for displaying the current clockface of device 600. In some embodiments, the criteria for re-enteringthe restricted mode includes the condition that corresponds to a triggerfor displaying the current clock face of device 600 (e.g., device 600does not re-enter the restricted mode until receiving a request todisplay the current clock face, even if other conditions have been met(e.g., inactivity criteria)).

Turning to FIG. 6T, clock face 614 is displayed while device 600 is notoperating in the restricted mode and the current time does notcorrespond to a predefined time range. In response to detecting input610 p (e.g., an upward swipe gesture on touch-sensitive display 602),device 600 displays user interface 628 (e.g., a control interface) withaffordances for controlling various functions of device 600, asillustrated in FIG. 6U. In response to detecting selection of affordance628-1 (e.g., a tap gesture 610 q on touch-sensitive display 602 at anaffordance corresponding to the restricted mode), device 600 enters therestricted mode and displays restricted clock face 618. In someembodiments, in response to detecting selection of affordance 626-1,device 600 displays user interface 626 as shown in FIG. 6S, except thataffordance 626-1 is selectable (e.g., not greyed out), such thatselection of affordance 626-1 causes device 600 to enter the restrictedmode and display restricted clock face 618. In these ways, a user canvoluntarily activate the restricted mode via inputs at device 600. Insome embodiments, activating the restricted mode manually as illustratedin FIGS. 6T-6U causes device 600 to remain in the restricted modeindefinitely until a user manually exits the restricted mode. In someembodiments, if a user manually activates the restricted mode and device600 remains in the restricted mode until the current time corresponds tothe predefined time range, device 600 will deactivate the restrictedmode upon expiration of the predefined time range (e.g., even if theuser has not manually deactivated the restricted mode). In someembodiments, if a user manually activates the restricted mode and device600 remains in the restricted mode until the current time corresponds tothe predefined time range, device 600 will remain in the restricted modeupon expiration of the predefined time range (e.g., until the restrictedmode is manually deactivated).

After device 600 enters the restricted mode at 3:30 PM as illustrated inFIG. 6V, device 600 remains in the restricted mode. While device 600 isstill in the restricted mode, device 600 detects input 610 r (e.g., adepression of depressible and rotatable input device 603) at 4:00 PM, asillustrated in FIG. 6W. In response to detecting input 610 r, device 600displays user interface 630 (FIG. 6X) including information regardingthe restricted mode. User interface 630 includes title 630-1 (“EXITRESTRICTED MODE”), message 630-2 indicating how long device 600 has beenin the restricted mode (“YOU'VE BEEN IN RESTRICTED MODE FOR 30 MIN”),and affordances 630-3 and 630-4. In user interface 630, displaying howlong device 600 has been in the restricted mode encourages some users toremain in the restricted mode or re-enter the restricted mode in thefuture (e.g., a user might be rewarded by his or her parents for notusing certain features of a device during a time intended for studying).

In contrast to user interface 620 (which is displayed while device 600is in the restricted mode due to a current time corresponding to apredefined time range), user interface 630 is displayed while device 600is in the restricted mode due to manual input (e.g., selection ofaffordance 628-1). That is, in the illustrated embodiment, the responseof device 600 to detecting input while operating in the restricted mode(or while displaying restricted clock face 618) depends on theconditions under which the restricted mode was entered (e.g., whetherdevice 600 is operating in the restricted mode due to a predefinedcondition or voluntarily user input at device 600).

In FIG. 6X, device 600 detects input 610 s (e.g., a rotation ofdepressible and rotatable input device 603). In response to detectinginput 610 s, device 600 scrolls user interface 630, as shown in FIG. 6Y.In some embodiments, in response to detecting input 610 t (e.g., a tapgesture on affordance 630-4), device 600 exits the restricted mode. Insome embodiments, after selection of affordance 630-4, device 600 willnot automatically re-enter the restricted mode or re-display restrictedclock face 618 in response to inactivity criteria being met, e.g., sincethe restricted mode was entered manually. In some embodiments, device600 will re-enter the restricted mode and re-display restricted clockface 618 in response to inactivity criteria being met, until therestricted mode is deactivated via affordance 626-1 on user interface626 in FIG. 6S.

FIG. 6Z illustrates a technique for exiting the restricted modeaccording to some embodiments. In response to detecting input 610 i(FIG. 6M), input 610 j (FIG. 6N), input 610 r (FIG. 6W), or input 610 s(FIG. 6X), device 600 displays user interface 632, which indicates thatdevice 600 is exiting the restricted mode or will exit the restrictedmode in response to rotation of depressible and rotatable input device603. In response to detecting input 610 u in FIG. 6Z (e.g., a rotationof depressible and rotatable input device 603), device 600 exits therestricted mode. The technique depicted by FIG. 6Z illustrates that, insome embodiments, device 600 exits the restricted mode in response to arotation of depressible and rotatable input device 603 directly fromrestricted clock face 618 or indirectly from restricted clock face 618(e.g., via user interfaces 620 or 630).

FIGS. 6AA-6AC illustrate techniques for viewing information regarding arestricted mode and setting parameters for a restricted mode (e.g., therestricted mode on device 600).

FIG. 6AA illustrates device 650 (e.g., device 100 or 300). In someembodiments, device 650 is paired with device 600 (e.g., there is adirect communication link between device 600 and 650) and/or associatedwith an account (e.g., user account) that is also associated with device600.

In FIG. 6AA, device 650 displays user interface 634 (e.g., a Screen Timesettings menu). User interface 634 includes item 634-1 (e.g., anaffordance) corresponding to a user interface associated with arestricted mode. In response to detecting selection of item 634-1 (e.g.,tap gesture 610v on item 634-1), device 650 displays user interface 636depicted in FIG. 6AB. User interface 636 includes items 636-1 and 636-2(e.g., affordances) associated with restricted mode information (e.g.,settings) corresponding to respective users. For example, item 636-1corresponds to restricted mode information associated with a user Emma.In the illustrated embodiment, the items are listed according to users(e.g., Emma, Johnny, etc.). In some embodiments, the items are listedaccording to particular devices (e.g., Emma's watch, Emma's phone,Johnny's watch).

In response to detecting input 610 w (e.g., a tap gesture on item636-1), device 650 displays user interface 638 illustrated in FIG. 6AC.User interface 638 includes information for a restricted mode for userEmma. In some embodiments, user interface 638 aggregates data frommultiple devices associated with user Emma. In some embodiments, userinterface 638 displays information on a per device basis. User interface638 includes affordance 638-1 (e.g., toggle button) for activating anddeactivating a restricted mode for Emma's devices (e.g., devicesassociated with Emma, devices associated with a user account associatedwith Emma). In some embodiments, selecting affordance 638-1 turns on arestricted mode for Emma's devices. In some embodiments, turning on therestricted mode via device 650 causes Emma's device(s) to activate arestricted mode (e.g., selecting affordance causes data to be sent toEmma's devices that cause Emma's devices to activate a restricted mode).In some embodiments, turning on the restricted mode via device 650causes Emma's devices to activate a restricted mode according to adefined schedule. In the illustrated embodiment, a restricted mode forEmma's devices is configured to be activated from 8 AM to 3 PM (e.g.,the restricted mode for Emma's devices has a predefined time range of 8AM to 3 PM such that Emma's devices operate in the restricted modebetween 8 AM and 3 PM).

In some embodiments, the settings for a restricted mode can beconfigured according to a custom schedule. User interface 638 includesaffordance 638-4 for displaying information (e.g., instructions) forcustomizing when Emma's devices are restricted. In response to detectingselection of affordance 638-2 (“CUSTOM”), device 650 displays a userinterface for editing/setting a customizable schedule according to whichEmma's devices will operate in the restricted mode. For example, device650 provides a user interface to customize the restricted mode scheduleper day (e.g., “8 AM-3 PM on Monday and 7 AM-2:30 PM on Tuesday” or “M-F7:30 AM-3 PM and Sat-Sun OFF”). In some embodiments, the predefined timerange is defined in accordance with a schedule that specifies differenttime ranges for different days of the week.

User interface 638 includes report log 638-3 showing exit events(referred to in user interface 638 as “UNLOCKS”) indicating times anddurations when user Emma's devices exited the restricted mode. Asdescribed above, devices remote from device 650 (e.g., device 600) canrecord data representing an indication the remote device has ceasedoperating in the restricted mode. This data is obtained by device 650and used to generate report log 638-3. In some embodiments, the recordeddata is transmitted (directly or indirectly) to device 650. In someembodiments, the recorded data is obtained when the remote device exitsthe restricted mode. In some embodiments, the recorded data is obtainedwhen the remote device re-enters the restricted mode. In someembodiments, the recorded data is obtained periodically (e.g., everyfive minutes, every hour, or at the end of the day or the end of theweek).

Report log 638-3 groups exit events by day (e.g., “TODAY”, “YESTERDAY”).In some embodiments, user interface 638 can be scrolled to displayadditional exit events (e.g., exit events for days prior to“YESTERDAY”). In some embodiments, report log 638-3 groups exit eventsby restricted mode period (e.g., if there is more than one predefinedtime range in a day (e.g., 8 AM-1 PM and “2 PM-3:30 PM), report log638-3 groups exit events by predefined time range). Report log 638-3includes exit event items 638-3 a through 638-3 f that indicate the timethe restricted mode was exited (unlocked) and the duration of the exitevent (e.g., how long the restricted mode was unlocked). In someembodiments, report log 638-3 includes additional information comparedto report log 626-2 displayed on device 600 (e.g., since device 650 hasa larger display size). For example, in some embodiments, report log638-3 includes an indication of a device associated with an exit eventitem (e.g., an icon representing a laptop, phone, or watch to indicatewhich device (or type of device) exited the restricted mode at the timeand duration indicated in the corresponding exit event item). In someembodiments, report log 626-2 displayed on device 600 includes anindication of a device associated with an exit event item.

In some embodiments, if device 650 is associated with the user Emma andis configured to operate in a restricted mode according to the scheduleindicated on user interface 638, report log 638-3 includes exit eventitems corresponding to times and durations when device 650 exited therestricted mode.

FIG. 7 is a flow diagram illustrating a method for operating anelectronic device in a restricted mode of operation in accordance withsome embodiments. Method 700 is performed at a device (e.g., 100, 300,500, 600, 650) with a display device. Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way fortransitioning between user interfaces. The method reduces the cognitiveburden on a user for transitioning between user interfaces, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to transition between user interfacesautomatically and more efficiently conserves power and increases thetime between battery charges.

An electronic device (e.g., 600) with a display device (e.g., 602),display (702) via the display device, a first user interface (e.g., 604)(e.g., a first clock face) of a respective type of user interface (e.g.,a current clock face) of the electronic device. In some embodiments, thefirst user interface of a respective type of user interface includes oneor more elements (e.g., 604-1, 604-2, 604-3) in a first arrangement(e.g., at least a first element and a second element in a firstarrangement). In some embodiments, the first element displays a firsttype of information (e.g., time) and the second element displays asecond type of information (e.g., information from a health or musicapplication). In some embodiments, the first user interface is agraphical user interface including a clock face with an indication oftime and, optionally, one or more user interface elements that representinformation other than time (e.g., complications).

In some embodiments, the respective type of user interface is a clockface.

In some embodiments, the electronic device detects (704) a sequence(e.g., 610 a, 610 b, and/or 610 c) of one or more inputs (e.g., contactson a touch-sensitive display and/or activation (e.g., depression orrotation) of a rotatable input mechanism) corresponding to a request tochange the current user interface (e.g., a current clock face) of arespective type of user interface of the electronic device (e.g., entera user interface editing mode and/or a user interface selection mode,edit a visual element of the first user interface or select a differentuser interface, and confirm selection of the edited or different userinterface). In some embodiments, at least one input (e.g., 601 a) of thesequence of one or more inputs is detected while the first userinterface is displayed.

In some embodiments, in response to detecting the sequence of one ormore inputs corresponding to the request to change the current userinterface of a respective type of user interface of the electronicdevice, the electronic device displays (706) via the display device, asecond user interface (e.g., 608) of the respective type of userinterface as the current user interface of a respective type of userinterface of the electronic device. In some embodiments, the second userinterface of a respective type of user interface includes one or moreelements (e.g., 608-1, 608-2, 608-3, 608-4, 608-5, and 608-6) that aredifferent from the one or more elements of the first user interface of arespective type of user interface and/or are in a different arrangementthan the first arrangement of the one or more elements of the first userinterface of a respective type of user interface (e.g., the second userinterface is an edited (customized) version of the first user interface(e.g., user-selected colors and/or complications for a predefinedlayout). In some embodiments, the second user interface is a differentstyle of user interface (e.g., the user can customize the user interfaceby selecting a particular (the second) user interface). In someembodiments, a style of user interface is defined by user interfaceelements on the user interface (e.g., number and types ofcomplications), layout of the user interface (e.g., arrangement ofelements), or the indication of time (e.g., digital or analog, in thecase of a clock face). In some embodiments, the sequence of one or moreinputs correspond to selection of features of the second user interface.

Displaying a second user interface with one or more elements that aredifferent from the one or more elements of the first user interfaceand/or are in a different arrangement than the first arrangement of theone or more elements of the first user interface in response todetecting a sequence of one or more inputs provides additional controloptions and customization of the user interface of the device. Providingadditional control options and customization of the user interfaceenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by providing a relevant interface andhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second user interface of a respective type ofuser interface includes a first affordance (e.g., 614-1) correspondingto an application (e.g., a workout application). In some embodiments,while displaying the second user interface of a respective type of userinterface, the electronic device detects an input (e.g., 610 h)corresponding to selection of the first affordance. In some embodiments,in response to detecting the input corresponding to selection of thefirst affordance, the electronic device launches the application (e.g.,616). In some embodiments, in contrast to the second user interface, auser interface (e.g., 618) corresponding to a restricted mode includesno graphical elements (e.g., affordances) that can be selected to launchcorresponding applications or functions.

In some embodiments, while displaying the second user interface of arespective type of user interface, the electronic device detects a thirdsequence of one or more inputs (e.g., contacts on a touch-sensitivedisplay and/or activation (e.g., depression or rotation) of a rotatableinput mechanism). In some embodiments, in response to detecting thethird sequence of one or more inputs while displaying the second userinterface of a respective type of user interface, the electronic deviceperforms an operation (e.g., opens an application, displays a dock ofrecently opened or designated (e.g., favorite) applications, displays anapplication springboard (e.g., 622, a plurality of icons for launchingcorresponding applications), displays a notification center (e.g., alist of notifications), transitions to a system space different from thecurrent system space, edits the current user interface or enter a userinterface editing or selection mode, or launches an applicationcorresponding to a complication). In some embodiments, a Do Not Disturbmode is enabled when a restricted mode is active. In some embodiments,while displaying a third user interface (e.g., restricted clock face618) of a respective type of user interface, the electronic devicedetects the third sequence of one or more inputs (e.g., the same type ofinputs in the same order that were detected while displaying the seconduser interface). In some embodiments, in response to detecting the thirdsequence of one or more inputs while displaying the third user interfaceof a respective type of user interface, the electronic device foregoesperformance of the operation. In some embodiments, operations that canbe performed while the electronic device is not operating in arestricted mode (e.g., sending e-mail and text messages, accessing a webbrowsing application, presenting notifications) cannot be performedwhile the electronic device is operating in a restricted mode (e.g., theelectronic device must exit the restricted mode in order to be able toperform the operations). In some embodiments, the performance of anoperation is modified while in the restricted mode (e.g., notificationof a phone call is presented only after multiple call attempts arereceived instead of on a first attempt).

In some embodiments, prior to detecting an occurrence of a conditionthat corresponds to a trigger for displaying the current user interfaceof a respective type of user interface of the electronic device, theelectronic device displays a user interface (e.g., 616) of a firstapplication (e.g., an application that is other than an application forgenerating clock faces; an application that is not part of the operatingsystem). In some embodiments, displaying the third user interface (e.g.,618) of a respective type of user interface includes ceasing to displaythe user interface of the first application. In some embodiments,ceasing to display the user interface of the first application includessuspending the first application or closing the first application.

In some embodiments, after changing the current user interface of arespective type of user interface of the electronic device to the seconduser interface of a respective type of user interface, the electronicdevice detects (708) the occurrence of a condition (e.g., a tap, wristraise, press of a button, closing of an application, or the like) thatcorresponds to a trigger for displaying the current user interface of arespective type of user interface of the electronic device.

In some embodiments, in response (710) to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current timecorresponds to a predefined time range (e.g., the current time is withina predefined time range; absolute time range (e.g., 9 am-3 pm) and/orrelative time range (e.g., within a defined amount of time (e.g., 1hour) from an event or a defined time), the electronic device displays(712) via the display device, a third user interface (e.g., 618) of arespective type of user interface (e.g., a third clock face) differentfrom the first user interface of a respective type of user interface andthe second user interface of a respective type of user interface (e.g.,if the second user interface is displayed when the current time reachesthe predefined time range, cease display of the second user interfaceand replace the second user interface with the third user interface).

Displaying a third user interface of a respective type of user interfacedifferent from the first user interface of a respective type of userinterface and the second user interface of a respective type of userinterface in accordance with a determination that a current timecorresponds to a predefined time range performs an operation when a setof conditions has been met without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the third user interface of a respective type ofuser interface includes a predefined set of elements (e.g., 618-1,618-2, 618-3, and 618-4) different from the one or more elements of thefirst user interface of a respective type of user interface and the oneor more elements of the second user interface of a respective type ofuser interface. In some embodiments, the predefined set of elementscannot be changed (e.g., edited or removed) in response to inputdetected at the electronic device. In some embodiments, the predefinedset of user interface elements (e.g., 618-1, 618-2, 618-3, and 618-4) ofthe third user interface has a predefined configuration or layout thatis different from a configuration or layout of the first set of userinterface elements of the second user interface. In some embodiments,the third user interface corresponds to a restricted mode and is notavailable when the restricted mode is not activated (e.g., the thirduser interface is not available in the face selection mode). In someembodiments, a user cannot select which user interface the third userinterface will be (e.g., the user cannot select which user interfacewill be displayed in the restricted mode). In some embodiments, thethird user interface is a static system setting. In some embodiments,features of the third user interface cannot be edited using theelectronic device, regardless of whether the restricted mode is activeor not (e.g., the third user interface is not available in the face editmode, or is displayed in edit mode but cannot actually be edited).

In some embodiments, while the current time corresponds to thepredefined time range and while the electronic device is operating in afirst mode (e.g., a restricted mode), the electronic device detects afifth sequence of one or more inputs (e.g., 610 i, 610 j, 610 k, 610 r,610 s, 610 t) (e.g., a sequence of inputs for exiting the restrictedmode; e.g., contacts on a touch-sensitive display and/or activation(e.g., depression or rotation) of a rotatable input mechanism). In someembodiments, the fifth sequence of one or more inputs includes at leastone input (e.g., 610 i, 610 r) that is detected while displaying thethird user interface of a respective type of user interface (e.g., thesequence of one or more inputs begins while the user interface isdisplayed). In some embodiments, in response to detecting the thirdsequence of one or more inputs, the electronic device exits the firstmode (e.g., FIGS. 6O-6P). In some embodiments, exiting the first modeincludes displaying the second user interface (e.g., 614) of arespective type of user interface.

In some embodiments, while the current time corresponds to thepredefined time range (e.g., the current time is still within thedesignated window for the restricted mode) and while the third userinterface of a respective type of user interface is not displayed (e.g.,FIGS. 6P-6S; the device has detected a request to exit the third userinterface and exit the restricted mode and has done so), the electronicdevice detects (e.g., automatically detects, detects without userinputs) that third interface of a respective type of user interfaceredisplay criteria are met. In some embodiments, the third userinterface redisplay criteria include one or more of the followingcriterion: user inputs have not been detected within a predeterminedamount of time or detecting an input corresponding to a request todeactivate display of content on the display device of the electronicdevice. In some embodiments, in response to detecting that the thirduser interface of a respective type of user interface redisplay criteriaare met, the electronic device displays (e.g., redisplays) the thirduser interface of a respective type of user interface.

In some embodiments, the third user interface of a respective type ofuser interface includes an analog indication of time (e.g., 618-1) and adigital indication of time (e.g., 618-3). In some embodiments, the thirduser interface includes an indication of the date (e.g., 618-2).

In some embodiments, an element (e.g., 618-1 a) of the analog indicationof time corresponding to a current hour of the current time is visuallyemphasized relative to elements of the analog indication of timecorresponding to hours other than the current hour.

In some embodiments, after ceasing to display the first user interface(e.g., 616) for the first application, the electronic device continuesto run the first application in the background (e.g., even if theelectronic device would not be allowed to start the first applicationduring the restricted mode in which the third user interface isdisplayed, the electronic device continues to run the first applicationin the background to enable the electronic device to finish theoperation that was being performed by the first application). In someembodiments, when the operation that was being performed by the firstapplication is completed, the electronic device does not allow a newoperation to be initiated for the first application while in therestricted mode. For example, if the user is running a workout trackingoperation for a workout application, the user is able to complete theworkout but is not able to start recording a new workout during thepredefined time range corresponding to the third user interface (e.g.,in the restricted mode). In some embodiments, if the application isdisplayed in the foreground when the current time reaches the predefinedtime range, the electronic device displays the third user interface andcontinues to run the application in the background.

In some embodiments, displaying the third user interface of a respectivetype of user interface includes: in accordance with a determination thatthe first application is running in the background, displaying the thirduser interface of a respective type of user interface with a graphicalelement (e.g., 618-5) corresponding to the first application (e.g., anicon indicating that the first application is running in thebackground). In some embodiments, displaying the third user interface ofa respective type of user interface includes: in accordance with adetermination that the first application is not running (e.g., is closedor suspended), displaying the third user interface of a respective typeof user interface without the graphical element corresponding to thefirst application. Displaying the third user interface without thegraphical element corresponding to the first application providesfeedback about the state of the first application (e.g., that the firstapplication is no longer running).

In some embodiments, the third user interface of a respective type ofuser interface includes an indication of a user's name (e.g., 618-4;full first and last name, first name only, full first name and lastinitial, initials only (e.g., first and last initial only)). In someembodiments, the user's name is customizable (e.g., via the electronicdevice or an external device). In some embodiments, the third userinterface of a respective type of user interface includes a digitalindication of time (e.g., 618-3).

In some embodiments, the predefined set of elements includes the entirethird user interface of a respective type of user interface (e.g., sincethe predefined set of user interface elements of the third userinterface cannot be changed in response to input detected at theelectronic device while operating in the restricted mode, none of theelements of the third user interface can be changed in response to inputdetected at the electronic device) and additional elements cannot beadded to the third user interface of a respective type of userinterface. In some embodiments, one or more elements (e.g., 618-4) ofthe third user interface (e.g., the user interface for the restrictedmode) are based on a user associated with the electronic device. Forexample, the third user interface includes an indication of a user'sname in some examples. In some embodiments, the name that appears on thethird user interface can be changed by editing a name associated withthe electronic device (e.g., the entire device, via a system levelsetting), but cannot be changed at the “user interface” level (e.g., inthe clock face edit mode). In some embodiments, a user cannot add, edit,or remove complications of the third user interface (e.g., clock face).In some embodiments, a user cannot add, edit, or remove the indicationof time of the third user interface. In some embodiments, an input(e.g., a contact on a touch-sensitive surface that is maintained longerthan a threshold amount of time (a long press) or a contact with acharacteristic intensity greater than a threshold intensity (a hardpress)) used to enter a user interface selection mode (e.g., clock faceselection mode) or a user interface edit mode (e.g., clock face editmode) when received while displaying other user interfaces does notcause the electronic device to enter the same mode when the same inputis received while displaying the third user interface.

In some embodiments, the third user interface of a respective type ofuser interface includes a distinguishing element (e.g., 618-1 b) (e.g.,a graphical element; a yellow ring with an outer diameter that issubstantially the same as a dimension of the display device (e.g., theouter diameter is greater than 90% of the width of the display)). Insome embodiments, the distinguishing element is a visuallydistinguishable portion of the third user interface of a respective typeof user interface (e.g., the first element is not an arbitrarily definedarea) and the distinguishing element is not included in the first userinterface of a respective type of user interface or the second userinterface of a respective type of user interface. In some embodiments,the first user interface and the second user interface (or any userinterface other than the third user interface) cannot be changed inresponse to input detected at the electronic device to include thedistinguishing element. In some embodiments, the distinguishing elementis displayed via the display device only while the third user interfaceis the current user interface (e.g., the first element is unique to thethird user interface). In some embodiments, the distinguishing elementis in a foreground of the third user interface (e.g., the distinguishingelement is not a background image).

In some embodiments, in response (710) to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current time does notcorrespond to the predefined time range, the electronic device displays(714) the second user interface of a respective type of user interface.

Displaying the second user interface in accordance with a determinationthat a current time does not correspond to the predefined time rangeperforms an operation when a set of conditions has been met withoutrequiring further user input. Performing an operation when a set ofconditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while the current time does not correspond to thepredefined time range (e.g., the current time is not within a window forthe restricted mode): the electronic device displays, via the displaydevice, a user interface (e.g., 628) (e.g., control center) including anaffordance (e.g., 628-1) for activating a restricted mode. In someembodiments, activating the restricted mode includes displaying thethird user interface. In some embodiments, the electronic device detectsan input (e.g., 610q) corresponding to selection of the affordance foractivating the restricted mode. In some embodiments, in response todetecting the input corresponding to selection of the affordance foractivating the restricted mode, the electronic device operates theelectronic device in the restricted mode (e.g., the restricted mode canbe activated via user input at the electronic device). In someembodiments, the predefined time range during which the electronicdevice is to operate in the restricted mode cannot be changed (e.g.,edited or turned on or off) via input at the electronic device (e.g.,the predefined time range can only be set using an external electronicdevice).

In some embodiments, the electronic device detects a second sequence(e.g., 610 a) of one or more inputs (e.g., tapping on a location where acomplication is located on the first user interface of the second userinterface). In some embodiments, in response to detecting the thirdsequence of one or more inputs: in accordance with the second sequenceof one or more inputs being detected while displaying the first userinterface of a respective type of user interface, the electronic deviceperforms an operation (e.g., launch an application corresponding to aselected complication). In some embodiments, in response to detectingthe second sequence of one or more inputs: in accordance with the secondsequence of one or more inputs being detected while displaying the thirduser interface of a respective type of user interface, the electronicdevice foregoes performance of the operation. In some embodiments, theelectronic device foregoes all operations (e.g., in response to the sameinput that causes the operation that is performed when the first userinterface is displayed, the electronic device does not perform anyoperation when the third user interface is displayed, not just theoperation performed when the first user interface is displayed). In someembodiments, the electronic device performs a second operation,different from the operation, in response to detecting the secondsequence of one or more inputs while the third user interface isdisplayed.

In some embodiments, after displaying the third user interface of arespective type of user interface (e.g., while or after operating in therestricted mode), the electronic device detects the occurrence of aninactivity condition (e.g., screen time-out or wrist down motion). Insome embodiments, after displaying the third user interface of arespective type of user interface (e.g., while or after operating in therestricted mode), in response to detecting the occurrence of theinactivity condition, the electronic device deactivates the displaydevice (e.g., ceasing to display content on the display, dimming thedisplay, putting the display to sleep, de-energizing illuminationelements of the display device, etc.). In some embodiments, the displayis a touchscreen display and deactivating the display includes ceasingto display content, without deactivating touch-sensing elements of thedisplay. In some embodiments, after displaying the third user interfaceof a respective type of user interface (e.g., while or after operatingin the restricted mode), after deactivating the display device, theelectronic device detects the occurrence of a condition (e.g., a tap,wrist raise, press of a button, closing of an application, or the like)that corresponds to a trigger for displaying a current user interface ofa respective type of user interface of the electronic device.

In some embodiments, after displaying the third user interface of arespective type of user interface (e.g., while or after operating in therestricted mode), in response to detecting the occurrence of a conditionthat corresponds to a trigger for displaying the current user interfaceof a respective type of user interface of the electronic device: inaccordance with a determination that a current time corresponds to thepredefined time range (e.g., the current time is within the restrictedmode window), the electronic device displays the third user interface(e.g., 618) of a respective type of user interface (e.g., display theface associated with the restricted mode). In some embodiments, afterdisplaying the third user interface of a respective type of userinterface (e.g., while or after operating in the restricted mode), inresponse to detecting the occurrence of a condition that corresponds toa trigger for displaying the current user interface of a respective typeof user interface of the electronic device: in accordance with adetermination that a current time does not correspond to the predefinedtime range (e.g., the current time is not within the restricted modewindow), the electronic device displays the second user interface (e.g.,608) of a respective type of user interface (e.g., display a userinterface that is not available in the restricted mode (e.g., acustomizable user interface)).

In some embodiments, while displaying the third user interface of arespective type of user interface, the electronic device detects afourth sequence (e.g., 610 i, 610 j, 610 k or 610 r, 610 s, 610 t) ofone or more inputs (e.g., contacts on a touch-sensitive display and/oractivation (e.g., depression or rotation) of a rotatable inputmechanism). In some embodiments, the fourth sequence of one or moreinputs correspond to a process for exiting the restricted mode, whichallows the electronic device to switch from the predefined third userinterface to a customizable user interface (e.g., the first or seconduser interface).

In some embodiments, in response to detecting at least one of the inputsin the fourth sequence of one or more inputs, the electronic devicedisplays an exit user interface (e.g., 620, 630) (e.g., the interface isoverlaid over a portion of the third user interface or replaces thethird user interface) with information for transition from a first mode,to a second mode, where the second mode includes one or more functionsnot accessible while in the first mode (e.g., switch to separate userinterface with title (“Exit Restricted Mode”), notice message (“Leavingappears in the School Time report”, “Time Left: 8 min”, or “You've beenin Restricted Mode for 2 hr and 5 min”), and Exit/Don't Exitaffordances; user inputs of the fourth sequence can include a press of abutton, rotation of a rotatable input mechanism, or a tap on thedisplay).

Displaying a user interface with information for transition from a firstmode to a second mode, where the second mode includes one or morefunctions not accessible while in the first mode provides improvedfeedback (e.g., by informing a user about a significant change inoperation). Providing improved feedback enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, ceasing to operate the electronic device in thefirst mode includes switching to an operational mode in which operationsthat are unavailable in the first mode can be performed. In someembodiments, ceasing to operate the electronic device in the first modeincludes displaying a different user interface with functionality notavailable in the initial user interface.

In some embodiments, the exit user interface includes a first portionthat includes an affordance (e.g., 620-5, 630-4) for exiting the firstmode. In some embodiments, the electronic device detects an input (e.g.,610 k, 610 t) corresponding to selection of the affordance for existingthe first mode. In some embodiments, in response to detecting the inputcorresponding to selection of the affordance for exiting the first mode,the electronic device displays the second user interface of a respectivetype of user interface (e.g., tap on exit affordance or press adepressible and rotatable input mechanism while exit affordance is infocus to cease operating the electronic device in the first mode andreturn to the second user interface).

Displaying the second user interface of a respective type of userinterface (e.g., instead of the third user interface associated with thefirst mode) in response to detecting an input corresponding to selectionof an affordance for exiting the first mode allows a user to provide anaffirmative input to exit the first mode. Displaying the affordance forexiting the first mode provides feedback to the user about theaffirmative input that can be taken to exit the first mode. Allowing auser to provide an affirmative input improves feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the exit user interface withoutdisplaying the first portion of the exit user interface that includesthe affordance for exiting the first mode (e.g., the user interfaceincludes multiple portions that are not simultaneously displayed), theelectronic device detects an input (e.g., 610 j, 610 s) corresponding toa request to scroll the exit user interface. In some embodiments, inresponse to detecting the input corresponding to a request to scroll theuser interface, the electronic device scrolls the user interface (e.g.,620, 630) to display the first portion of the user interface thatincludes the affordance for exiting the first mode (e.g., initially, theexit affordance is slightly or completely off screen so the user has toscroll before selecting it to avoid accidental activation).

Scrolling the user interface to display the first portion of the userinterface that includes the affordance for exiting the first mode inresponse to detecting a user input adds an additional action to performthe exiting process. Adding an additional input in this instanceenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the user interface that includes the affordance forexiting the first mode is displayed in response to detecting the atleast one of the inputs in a sequence of one or more inputs. In someembodiments, the user interface that includes the affordance for exitingthe first mode is displayed concurrently with presenting an alert (e.g.,620-2) indicating that the information indicating that the electronicdevice has exited the first mode will be reported to another user (e.g.,button is slightly off screen so user has to scroll before selecting itto avoid accidental activation).

In some embodiments, detecting the fourth sequence of one or more inputsfor exiting the restricted mode includes detecting a rotation of arotatable input mechanism (e.g., 603). In some embodiments, in responseto detecting the rotation of the rotatable input mechanism, theelectronic device displays the second user interface of a respectivetype of user interface (e.g., and ceases to operate the electronicdevice in the first mode). In some embodiments, the electronic deviceexits the first mode in response to rotation of the rotatable inputmechanism while the third user interface is displayed. In someembodiments, the electronic device replaces the third user interfacewith a different user interface (e.g., 620) in response to a first inputand then exits the first mode in response to rotation of the rotatableinput mechanism while the different user interface is displayed (e.g.,the rotation of the rotatable input mechanism is a confirmation input).

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, methods 800 and 1000optionally include one or more of the characteristics of the variousmethods described above with reference to method 700. For example,operations 702-706 related to changing a user interface are optionallyperformed prior to operation 802 of method 800. As another example,operations 708-712 can be used to display a user interface of arespective type of user interface in operation 804 of method 800. Forbrevity, these details are not repeated below.

FIG. 8 is a flow diagram illustrating a method for providing alertsusing an electronic device in accordance with some embodiments. Method800 is performed at a device (e.g., 100, 300, 500, 600, 650) with adisplay device. Some operations in method 800 are, optionally, combined,the orders of some operations are, optionally, changed, and someoperations are, optionally, omitted.

As described below, method 800 provides an intuitive way for providingalerts.

The method reduces the cognitive burden on a user for reporting alerts,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to provide alerts,faster, automatically, and more efficiently conserves power andincreases the time between battery charges.

An electronic device (e.g., 600) with a display device (e.g., 602)operates (802) in a first mode (e.g., a restricted mode in which amajority of operations available in other modes of operation of theelectronic device are not available).

In some embodiments, while operating the electronic device in the firstmode: the electronic device displays (804), via the display device(e.g., 602), a user interface (e.g., 618) of a respective type of userinterface (e.g., a clock face).

In some embodiments, while operating the electronic device in the firstmode: the electronic device detects (806) a first sequence (e.g., 610 i,610 j, 610 k) of one or more inputs (e.g., contacts on a touch-sensitivedisplay and/or activation (e.g., depression or rotation) of a rotatableinput mechanism) corresponding to a request to exit the first mode, thefirst sequence of one or more inputs including at least one input (e.g.,610 i) that is detected while displaying the user interface of arespective type of user interface (e.g., the sequence of one or moreinputs begins while the user interface is displayed).

In some embodiments, the respective type of user interface is a clockface (e.g., 618).

In some embodiments, the electronic device includes a touch-sensitivesurface device (e.g., separate from or as a part of the display device),and the first sequence of one or more inputs includes a tap gesture onthe touch-sensitive surface (e.g., touch-sensitive display).

In some embodiments, the electronic device includes a rotatable anddepressible input mechanism (e.g., 603) that is rotatable relative to ahousing of the electronic device (e.g., the rotatable and depressibleinput mechanism rotates around an axis parallel to a display of thedisplay device), and the first sequence of one or more inputs includes adepression of the rotatable and depressible input mechanism.

In some embodiments, while operating the electronic device in the firstmode: after (e.g., in response to) detecting at least one of the inputsin the first sequence of one or more inputs and prior to ceasing tooperate the electronic device in the first mode, the electronic devicepresents (808) an alert (e.g., 620-2) indicating that informationindicating that the electronic device has exited the first mode will bereported to another user.

Presenting an alert indicating that information indicating that theelectronic device has exited the first mode will be reported to anotheruser provides improved feedback to the user about the effects ofproceeding with exiting the first mode of the electronic device.Providing improved feedback enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, after (e.g., in response to) detecting at least oneof the inputs in the first sequence of one or more inputs and prior toceasing to operate the electronic device in the first mode, theelectronic device displays, via the display device, an indication (e.g.,630-2) of a duration that the electronic device has been operating inthe first mode. In some embodiments, the indication of the duration thatthe electronic device has been continuously operating in the first modeis displayed concurrently with presenting the alert indicating thatinformation indicating that the electronic device has exited the firstmode will be reported to another user.

In some embodiments, while operating the electronic device in the firstmode: after presenting the alert, the electronic device detects (810) asecond sequence (e.g., 610 j, 610 k) of one or more inputs. In someembodiments, the second sequence of one or more inputs is a rotation ofa rotatable mechanism of the electronic device. In some embodiments, thealert includes an affordance (e.g., 620-5) for exiting the first mode,and the second sequence of one or more inputs includes an inputcorresponding to selection of the affordance.

Including an affordance for exiting the first mode provides improvedvisual feedback about the input(s) that can be used to exit the firstmode. Providing improved visual feedback enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the affordance is an exit affordance. In someembodiments, the selection of the affordance is a tap on the exitaffordance or a press of a depressible input mechanism while the exitaffordance is in focus. In some embodiments, the exit affordance isdisplayed in response to detecting the at least one of the inputs in thefirst sequence of one or more inputs. In some embodiments, the exitaffordance is displayed concurrently with presenting the alertindicating that the information indicating that the electronic devicehas exited the first mode will be reported to another user.

In some embodiments, presenting the alert includes displaying an alertuser interface (e.g., 620) (e.g., overlaid over a portion of the userinterface or replacing the user interface), and the alert user interfaceincludes a first portion that includes the affordance for exiting thefirst mode. In some embodiments, while displaying the alert userinterface without displaying the first portion of the alert userinterface that includes the affordance for exiting the first mode (e.g.,the user interface includes multiple portions that are notsimultaneously displayed), the electronic device detects an input (e.g.,610 j) corresponding to a request to scroll the alert user interface. Insome embodiments, in response to detecting the input corresponding to arequest to scroll the alert user interface, the electronic devicescrolls the alert user interface to display the first portion of thealert user that includes the affordance for exiting the first mode(e.g., initially, the exit affordance is slightly or completely offscreen so the user has to scroll before selecting it to avoid accidentalactivation). In some embodiments, the user interface is displayed inresponse to detecting the at least one of the inputs in the firstsequence of one or more inputs. In some embodiments, the user interfaceis displayed concurrently with presenting the alert indicating that theinformation indicating that the electronic device has exited the firstmode will be reported to another user.

In some embodiments, while operating the electronic device in the firstmode: in response to detecting the second sequence of one or more inputsand in accordance with a determination that the second sequence of oneor more inputs corresponds to a request to exit the first mode, theelectronic device ceases (812) to operate the electronic device in thefirst mode (e.g., exits the first mode). In some embodiments, ceasing tooperate the electronic device in the first mode includes switching to anoperational mode in which operations that are unavailable in the firstmode can be performed. In some embodiments, ceasing to operate theelectronic device in the first mode includes displaying a different userinterface (e.g., 618) with functionality not available in the initialuser interface.

Exiting the first mode allows the electronic device to performadditional functionality and provides improved feedback to user inputs.Allowing the electronic device to perform additional functionality andproviding improved feedback to user inputs enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the second sequence of oneor more inputs and in accordance with a determination that the secondsequence of one or more inputs corresponds to a request to exit thefirst mode, the electronic device records (e.g., for transmission to asecond electronic device; begins to record (e.g., continues to recordwhile the device remains outside of the first mode) data representing anindication that the electronic device has ceased operating in the firstmode (e.g., the recorded data is transmitted to an external device; thedata causes a report of the exit event to be displayed at an externaldevice). In some embodiments, the information is transmitted uponexiting the first mode (e.g., in response to detecting the secondsequence of one or more inputs and in accordance with a determinationthat the second sequence of one or more inputs corresponds to a requestto exit the first mode). In some embodiments, the information is nottransmitted upon exiting the first mode (e.g., the information istransmitted when the restricted mode is entered again or at the end ofthe day or the end of the week).

In some embodiments, recording the data representing an indication thatthe electronic device has ceased operating in the first mode includesrecording a time at which the electronic device ceased operating in thefirst mode in response to detecting the second sequence of one or moreinputs, and a duration of time for which the electronic device was notoperating in the first mode (e.g., an amount of time between exiting thefirst mode and re-entering the first mode).

Recording data representing an indication that the electronic device hasceased operating in the first mode allows the electronic device tonotify another user (e.g., a parent) that the electronic device hasceased operating in the first mode. In some embodiments, the data isrecorded automatically, reducing the number of inputs needed to notifyanother user. Providing the ability to notify another user whilereducing the number of inputs enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device displays, via the displaydevice, a report log (e.g., 626-2) indicating one or more occurrences ofan electronic device exiting a restricted mode (e.g., the first mode onthe electronic device). In some embodiments, a restricted mode onanother device is technically a different mode (e.g., a differentversion of the first mode), but exiting of the restricted mode on theother device is indicated in the report log. In some embodiments, thereport log includes an indication of the time at which the electronicdevice ceased operating in the first mode in response to detecting thesecond sequence of one or more inputs and an indication of the durationof time for which the electronic device was not operating in the firstmode (e.g., in a settings menu). In some embodiments, the time andduration information is available while the electronic device isoperating in the first mode. In some embodiments, the time and durationinformation are not available while the electronic device is operatingin the first mode, but are available when the electronic device is notoperating in the first mode. In some embodiments, the time and durationinformation are displayed in response to a sequence of one or moreinputs (e.g., by navigating to a Settings menu).

In some embodiments, the report log further includes an indication of atime at which a second electronic device (e.g., a smartphone, tablet, oranother watch associated with the user) ceased operating in a restrictedmode and an indication of a duration of time for which the secondelectronic device was not operating in the restricted mode. In someembodiments, the report log is displayed on another device (e.g., adevice with an account associated with the electronic device and thesecond device). In some embodiments, the report log is displayed in asettings menu through which a user can also adjust settings of therestricted mode (on/off, restricted times, etc.).

In some embodiments, the electronic device detects a third sequence ofone or more inputs (e.g., contacts on a touch-sensitive display and/oractivation (e.g., depression or rotation) of a rotatable inputmechanism). In some embodiments, in response to detecting the thirdsequence of one or more inputs: in accordance with a determination thatthe electronic device is not operating in the first mode, the electronicdevice performs an operation (e.g., opens an application, displays adock of recently opened or designated (e.g., favorite) applications,displays an application springboard (e.g., a plurality of icons forlaunching corresponding apps), display a notification center (e.g., alist of notifications), transitions to a system space different from thecurrent system space, edits the current user interface or enters a userinterface editing or selection mode, launches an applicationcorresponding to a complication). In some embodiments, in response todetecting the third sequence of one or more inputs: in accordance with adetermination that the electronic device is operating in the first mode,the electronic device foregoes performance of the operation. In someembodiments, operations that can be performed while the electronicdevice is not operating in the first mode cannot be performed in thefirst mode (e.g., the electronic device must exit the first mode inorder to be able to perform the operations).

Note that details of the processes described above with respect tomethod 800 (e.g., FIG. 8) are also applicable in an analogous manner tothe methods described above. For example, methods 700 and 1000optionally include one or more of the characteristics of the variousmethods described above with reference to method 800.

For example, some or all of operations 806-812 related to presenting analert and exiting the first mode are optionally performed while orsubsequent to displaying the third user interface in operation 712 ofmethod 700. As another example, operations 708-712 can be used todisplay a user interface of a respective type of user interface inoperation 804 of method 700.

FIGS. 9A-9AI illustrate exemplary user interfaces for configuring anexternal device, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 10.

FIG. 9A depicts device 900, which is a smartphone with display 902.Display 902 includes a touch-sensitive surface on which device 900 candetect user gestures (e.g., tap, swipe, drag). In some embodiments,device 900 includes one or more features of device 100, 300, or 500.

At FIG. 9A, device 900 displays user interface 904 for guiding a userthrough a setup process for an external device (e.g., smartwatch, device600). User interface 904 includes options for choosing the intended userof the smartwatch, and thus the user account to be associated with thesmartwatch. In particular, user interface 904 includes affordance 906 a,which, when selected, initiates a setup process for configuring theexternal device to be associated with a first user account (e.g., a useraccount that is already associated with device 900). Additionally, userinterface 904 includes affordance 906 b, which, when selected, initiatesa setup process for configuring the external device to be associatedwith a second user account (e.g., a user account other than the useraccount that is already associated with device 900).

As shown in FIG. 9A, the user performs a tap gesture to identify someoneother than the user of device 900 as the intended user of the externaldevice. As a result, device 900 detects input 908 at affordance 906 b.In response to detecting input 908, device 900 initiates a setup processfor configuring the external device to be associated with the seconduser account.

In some embodiments, instead of detecting input 908 at affordance 906 b,device 900 detects an input (e.g., a tap gesture) at affordance 906 a.In some embodiments, in response to detecting the input at affordance906 a, device 900 initiates a setup process for configuring the externaldevice to be associated with the first user account (e.g., the useraccount of device 900).

As depicted on the left side of FIG. 9B, after initiating the setupprocess for configuring the external device to be associated with thesecond user account, device 900 displays user interface 910 a forpairing the external device to device 900. User interface 910 a includescontent 912 a, which prompts the user to hold the external device up tothe camera of device 900.

As depicted on the right side of FIG. 9B, in some embodiments, afterinitiating the setup process for configuring the external device to beassociated with the first user account instead of the second useraccount, device 900 displays user interface 910 b for pairing theexternal device to device 900. User interface 910 b includes content 912b, which differs from content 912 a in that it prompts the user to wearthe external device in addition to prompting the user to hold theexternal device up to the camera of device 900. Content 912 b promptsthe user to wear the external device because the external device isbeing configured for the user of device 900. In contrast, content 912 adoes not prompt the user to wear the external device because theexternal device is not being configured for the user of device 900.

At FIG. 9C, after the external device is paired (or in wirelesscommunication) with device 900, device 900 continues with the setupprocess and displays user interface 914 for continuing with configuringthe external device to be associated with the second user account. Userinterface 914 includes a visual indication that the external device isbeing setup for a family member (e.g., someone other than the user ofdevice 900) without explicitly identifying the family member, as device900 does not yet have this identifying information. While displayinguser interface 914, device 900 detects input 916 a at affordance 916 band, in response, continues with the setup process.

At FIG. 9D, after detecting input 916 a, device 900 displays userinterface 918 for associating a user account with the external device.User interface 918 includes affordances 920 a-920 b. In someembodiments, device 900 detects an input (e.g., tap gesture) ataffordance 920 b. In some embodiments, in response to detecting theinput at affordance 920 b, device 900 displays one or more text fieldsfor receiving information to create a new user account.

Returning to FIG. 9D, because the intended user of the external devicehas an existing user account, the user performs a tap gesture toassociate the external device with an existing user account. As aresult, device 900 detects input 919 at affordance 920 a. In response todetecting input 919, device 900 initiates a process for selecting anexisting user account.

As depicted on the left side of FIG. 9E, after initiating the processfor selecting an existing user account, device 900 displays userinterface 922 a. User interface 922 a includes representations 923 a-923c of existing user accounts and option 923 d, which, when selected,results in displaying one or more text fields for receiving informationto identify an existing user account. In some embodiments, the existinguser accounts (e.g., corresponding to representations 923 a-923 c) areassociated with the user account of device 900. For example, theexisting user accounts and the user account of device 900 are part ofthe same group (e.g., family group).

As depicted on the right side of FIG. 9E, in some embodiments, device900 displays user interface 922 b instead of user interface 922 a whenthe external device is being configured to be associated with the firstuser account. In particular, after initiating the process for selectingan existing user account, device 900 displays user interface 922 b,which prompts the user for login information (e.g., credentials,password) corresponding to the first user account instead of, forexample, displaying representations 923 a-923 c.

Returning to the left side of FIG. 9E, the user performs a tap gestureto select the user account belonging to Emma Appleseed as the seconduser account. As a result, device 900 detects input 924 atrepresentation 923 b.

At FIG. 9F, in response to detecting input 924, device 900 continueswith the setup process and displays user interface 926 with information(e.g., name, email address, date of birth) corresponding to the seconduser account (e.g., the user account belonging to Emma Appleseed). Insome embodiments, the information is displayed in one or more textfields that can be edited via user input. It is noted that theinformation corresponding to the second user account is now available todevice 900, thereby enabling personalization for user interfaces laterin the setup process. Returning to FIG. 9F, the user performs a tapgesture to confirm the selection. As a result, device 900 detects input927 a at affordance 927 b. In response to detecting input 927 a, device900 confirms the selection of Emma's user account.

At FIG. 9G, after confirming the selection of Emma's user account,device 900 displays user interface 928 for creating a passcode (e.g.,security information) at the external device. The user performs a tapgesture to initiate a process for creating the passcode. As a result,device 900 detects input 929 a at affordance 929 b. In some embodiments,in response to detecting input 929 a, device 900 determines whether theage of the user corresponding to the second user account is below athreshold age (e.g., 6, 12, 18).

If the age of the user corresponding to the second user account is lessthan the threshold age, device 900 displays user interface 930 a withcontent 931 a, as shown in FIG. 9H. Content 931 a prompts the user ofdevice 900 to enter a passcode at the external device on behalf of theuser corresponding to the second user account. In contrast, in someembodiments, if the age of the user corresponding to the second useraccount is at least the threshold age, device 900 displays userinterface 930 b with content 931 b, as shown in FIG. 9I. Content 931 bprompts the user of device 900 to have the user corresponding to thesecond user account (e.g., John) enter a passcode at the externaldevice. In some embodiments, if the external device is being configuredto be associated with the first user account, device 900 does notdisplay user interface 930 a or 930 b, and instead prompts the user toenter a passcode for the user of device 900 (e.g., instead of on behalfof some other user).

Returning to FIGS. 9H-9I, in some embodiments, after the passcode hasbeen entered, device 900 determines whether the second user account isalready associated with a device (e.g., smartphone) that is capable ofbeing paired with the external device (e.g., smartwatch). In someembodiments, if the external device is being configured to be associatedwith the first user account, device 900 does not make thisdetermination.

At FIG. 9J, if the second user account is already associated with adevice capable of being paired with the external device, device 900displays user interface 932 a with options to either continue or abortthe setup process. In some embodiments, user interface 932 a does notinclude the option (e.g., affordance 933 b) to continue with the setupprocess. In some embodiments, if the second user account is not alreadyassociated with such a device, device 900 forgoes displaying userinterface 932 a and continues with the setup process (e.g., proceeds todisplaying the user interface 936 in FIG. 9K).

Returning to FIG. 9J, the user performs a tap gesture to continue withthe setup process. As a result, device 900 detects input 934 ataffordance 933 b. In response to detecting input 934, device 900continues with the setup process.

At FIG. 9K, continuing with the setup process, device 900 displays userinterface 936 for sharing wireless network information with the externaldevice. User interface 936 includes affordance 937 a, which, whenselected, initiates a process for transmitting current wireless networkinformation to the external device, where the current wireless networkinformation includes a network ID and password for the wireless networkthat device 900 is currently signed into. Additionally, user interface936 includes affordance 937 b, which, when selected, initiates a processfor transmitting wireless network information to the external device,where the wireless network information includes all network IDs andpasswords stored on device 900. In some embodiments, device 900 does notinclude one of affordance 937 a or affordance 937 b. In someembodiments, device 900 does not display user interface 936 if theexternal device is being configured to be associated with the first useraccount.

Returning to FIG. 9K, the user performs a tap gesture to share thecurrent wireless network information. As a result, device 900 detectsinput 938 at affordance 937 a and, in response, initiates a process fortransmitting the current wireless network information to the externaldevice.

As depicted on the left side of FIG. 9L, after transmitting the wirelessnetwork information, device 900 continues with the setup process anddisplays user interface 940 a for enabling location services. Asdiscussed above, device 900 has information about the second useraccount (e.g., the name of the user associated with the second useraccount). Using this information, device 900 displays user interface 940a with name 941, which identifies the user account for which theexternal device is being configured. Providing identifying informationduring the setup process can be helpful to the user of device 900, as itreminds the user of that the external device is being set up for someoneelse (e.g., Emma Appleseed).

As depicted on the right side of FIG. 9L, in some embodiments, device900 displays user interface 940 b instead of user interface 940 a if theexternal device is being configured to be associated with the first useraccount (e.g., a user account associated with the user of device 900).Since the external device is being setup for the user of device 900,user interface 940 b does not include information (e.g., name 941) thatidentifies the intended user of the external device.

To enable location services, the user performs a tap gesture ataffordance 942 a. As a result, device 900 detects input 942 b ataffordance 942 a, as shown on the left side of FIG. 9L. In response todetecting input 942 b, device 900 initiates a process for enablinglocation services at the external device.

As depicted on the left side of FIG. 9M, after initiating the processfor enabling location services, device 900 displays user interface 944 afor enabling a voice assistant at the external device. The user performsa tap gesture to enable the voice assistant. As a result, device 900detects input 945 b at affordance 945 a. In response to detecting input945 b, device 900 initiates a process for enabling a voice assistant atthe external device. Similar to FIG. 9L, device 900 displays a differentuser interface (e.g., 944 b) without name 941 if the setup process isfor configuring the external device to be associated with the first useraccount (e.g., a user account associated with the user of device 900).

After initiating the process for enabling the voice assistant, device900 displays user interface 946 a for setting up activity features atthe external device, as depicted on the left side of FIG. 9N. The userperforms a tap gesture to setup the activity features. As a result,device 900 detects input 947 b at affordance 947 a. In response todetecting input 945 b, device 900 initiates a process for setting upactivity features at the external device. Similar to FIG. 9L, device 900displays a different user interface (e.g., 946 b) without name 941 ifthe setup process is for configuring the external device to beassociated with the first user account (e.g., a user account associatedwith the user of device 900).

At FIG. 9O, after initiating the process for setting up activityfeatures, device 900 displays user interface 948 for configuringactivity sharing between the external device and device 900. In someembodiments, device 900 does not display user interface 948 if theexternal device is being configured to be associated with the first useraccount. Returning to FIG. 9O, device 900 detects input 949 b (e.g., tapgesture) at affordance 949 a.

At FIG. 9P, in response to detecting input 949 b, device 900 displaysuser interface 950 for setting a daily move goal for Emma. The userchooses a daily move goal and performs a tap gesture to set the dailymove goal at the external device. As a result, device 900 detects input951 b at affordance 951 a. In response to detecting input 951 b, device900 initiates a process for configuring the external device with thechosen daily move goal.

At FIG. 9Q, after initiating the process for configuring the externaldevice with the chosen daily move goal, device 900 displays userinterface 952 for enabling workout route tracking. Device 900 detectsinput 953 b (e.g., tap gesture) at affordance 953 a. In response todetecting input 953 b, device 900 initiates a process for enablingworkout route tracking at the external device.

As depicted on the left side of FIG. 9R, after initiating a process forenabling workout route tracking, device 900 displays user interface 954a for enabling sharing of health data between the external device anddevice 900. Device 900 detects input 955 b (e.g., tap gesture) ataffordance 955 a. In response to detecting input 955 b, device 900initiates a process for enabling sharing of health data between theexternal device and device 900. Similar to FIG. 9L, device 900 displaysa different user interface (e.g., 954 b) without name 941 if the setupprocess is for configuring the external device to be associated with thefirst user account (e.g., a user account associated with the user ofdevice 900).

At FIG. 9S, after initiating a process for enabling sharing of healthdata between the external device and device 900, device 900 displaysuser interface 956 a for enabling emergency features at the externaldevice. Device 900 detects input 957 b (e.g., tap gesture) at affordance957 a. In response to detecting input 957 b, device 900 initiates aprocess for enabling emergency features at the external device. Similarto FIG. 9L, device 900 displays a different user interface (e.g., 956 b)without name 941 if the setup process is for configuring the externaldevice to be associated with the first user account (e.g., a useraccount associated with the user of device 900).

At FIG. 9T, after initiating a process for enabling emergency featuresat the external device, device 900 displays user interface 958 a foridentifying emergency contacts. Device 900 detects input 959 b (e.g.,tap gesture) at affordance 959 a. In response to detecting input 959 b,device 900 enters the identified emergency contacts. Similar to FIG. 9L,device 900 displays a different user interface (e.g., 958 b) withoutname 941 if the setup process is for configuring the external device tobe associated with the first user account (e.g., a user accountassociated with the user of device 900).

At FIGS. 9U-9V, device 900 detects one or more inputs (e.g., 961 b, 963b) for configuring the external device with a digital medical ID card.While displaying user interface 960, device 900 detects input 961 b(e.g., tap gesture) at affordance 961 a. In response to detecting input961 b, device 900 displays user interface 962. While displaying userinterface 962, device 900 detects input 963 b (e.g., tap gesture) ataffordance 963 a. In response to detecting input 963 b, device 900initiates a process for configuring the external device with a digitalmedical ID card.

At FIGS. 9W-9X, after initiating the process for configuring theexternal device with a digital medical ID card, device 900 detects oneor more inputs (e.g., 965 b, 958 b) for adding photos to the externaldevice. While displaying user interface 964, device 900 detects input965 b (e.g., tap gesture) at affordance 965 a. In response to detectinginput 965 b, device 900 displays user interface 966 with representations967 a-967 g of photo albums. The user selects representation 967 f toadd the “Emma” album and its collection of photos to the externaldevice. Once representation 967 f is selected, device 900 detects input968 b (e.g., tap gesture) at done button 968 a. In response to detectinginput 968 b, device 900 initiates a process for adding the selectedalbum to the external device. In some embodiments, the selected albumcontinues to remain synced indefinitely between device 900 and theexternal device (e.g., if a photo is added to the selected album atdevice 900, that photo is also added to the external device).

At FIG. 9Y, after initiating the process for adding the selected photoalbum to the external device, device 900 continues with the setupprocess and displays user interface 970 for configuring applicationrestrictions at the external device. While displaying user interface970, device 900 detects input 971 b (e.g., tap gesture) at affordance971 a. In response to detecting input 971 b, device 900 initiates aprocess for configuring the external device with specified applicationrestrictions.

At FIGS. 9Z-9AA, after initiating the process for configuring theexternal device with specified application restrictions, device 900detects one or more inputs (e.g., 973 b, 975 b) to generate a contactcard for Emma Appleseed. While displaying user interface 972, device 900detects input 973 b at affordance 973 a. In response to detecting input973 b, device 900 displays user interface 974 with information aboutEmma Appleseed. While displaying user interface 974, device 900 detectsinput 975 b at done button 975 a. In response to detecting input 975 b,device 900 generates a contact card for Emma Appleseed.

At FIGS. 9AB-9AC, after generating the contact card for Emma Appleseed,device 900 displays user interface 976 for requesting access to managecontacts at the external device. While displaying user interface 976,device 900 detects input 977 b at affordance 977 a. In response todetecting input 977 b, device 900 transmits a request to manage thecontacts at the external device. Further in response to detecting input977 b, device 900 displays notification 979 c in user interface 978,which provides a visual indication that the request has been sent. Whiledisplaying user interface 978, device 900 detects input 979 b atconfirmation button 979 a. In response to detecting input 979 b, device900 completes the process for requesting access to manage contacts atthe external device.

At FIGS. 9AD-9AE, after completing the process for requesting access tomanage contacts at the external device, device 900 detects one or moreinputs (e.g., 981 b, 984 b) for adding contacts to the external device.While displaying user interface 980, device 900 detects input 981 b ataffordance 981 a. In response to detecting input 981 b, device 900displays user interface 982 with representations 983 a-983 h ofcontacts. The user selects representations 983 a-983 c and 983 e to addtheir corresponding contacts to the external device. Once the contactshave been selected, device 900 detects input 984 b (e.g., tap gesture)at done button 984 a. In response to detecting input 984 b, device 900initiates a process for adding the selected contacts to the externaldevice.

At FIGS. 9AF-9AG, after initiating the process for adding the selectedcontacts to the external device, device 900 detects one or more inputs(e.g., 987 b, 989 b) for configuring a restricted mode at the externaldevice. It is noted that a restricted mode at the external device isfurther described above with respect to FIGS. 6A-6AC. In someembodiments, a restricted mode is a mode in which a first set of one ormore functions available in an unrestricted mode is not available whilein the restricted mode, and in which a second set of one or morefunctions available in an unrestricted mode is available while in therestricted mode.

At FIG. 9AF, while displaying user interface 986, device 900 detectsinput 987 b at affordance 987 a. In response to detecting input 987 b,device 900 displays user interface 988, as shown in FIG. 9AG. Userinterface 988 includes one or more options for setting a restricted modeschedule at the external device. Once the schedule has been set, device900 detects user input 989 b at done button 989 a. In response todetecting user input 989 b, device 900 initiates a process forconfiguring the external device with the set restricted mode schedule.

At FIG. 9AH, after initiating the process for configuring the externaldevice with the set restricted mode schedule, device 900 displays userinterface 990 to indicate that the end of the setup process has beenreached. While displaying user interface 990, device 900 detects input991 b at confirmation button 991 a. In response to detecting input 991b, device 900 exits the setup process.

In some embodiments, device 900 enables sharing of one or more features(e.g., settings, data) with the external device if the external deviceis being configured to be associated with the first user account (e.g.,the user account associated with device 900). Accordingly, in someembodiments, device 900 displays user interface 992 in FIG. AI at somepoint during the setup process. In contrast, if the external device isbeing configured to be associated with the second user account (e.g., auser account other than the user account associated with device 900),device 900 forgoes displaying user interface 992 during the setupprocess.

FIG. 10 is a flow diagram illustrating a method for configuring a seconddevice using a first electronic device in accordance with someembodiments. Method 1000 is performed at a first device (e.g., 100, 300,500, 650, 900) with a display device. Some operations in method 1000are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 1000 provides an intuitive way forconfiguring a second device. The method reduces the cognitive burden ona user for configuring the second device, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to configure a second device faster and moreefficiently conserves power and increases the time between batterycharges.

In some embodiments, the first device (e.g., 900) displays (1002), viathe display device (e.g., 902), a setup user interface (e.g., 904) of asetup process for setting up a second device (e.g., 600 for configuringan external device). In some embodiments, the setup user interfaceincludes a first affordance (e.g., 906 a) (e.g., with a visualindication of the user for which the second device will be configured(e.g., text “set up for myself”)) and a second affordance (e.g., 906 b)(e.g., with a visual indication of the user for which the second devicewill be configured (e.g., with text “set up for a family member”)). Insome embodiments, activation of the first affordance results ininitiating a process for configuring a second device to be associatedwith a first user/user account (e.g., a user/user account of the firstdevice). In some embodiments, activation of the second affordanceresults in initiating a process for configuring the second device to beassociated with a second user/user account different from the firstuser/user account.

In some embodiments, while displaying, via the display device, the setupuser interface, the first device detects (1004) a first user input(e.g., 908, a gesture (e.g., tap, swipe), an audio input) selecting arespective account to be associated with the second device and while thefirst device is associated with a first account (e.g., the first deviceis associated with (configured for) the first account of the user of thefirst device, a user account).

After the respective account has been selected to be associated with thesecond device and during the setup process, the first device displays(1006), via the display device, a setup user interface (e.g., 940 a-940b, 944 a-944 b, 946 a-946 b, 954 a-954 b, 956 a-956 b, 958 a-958 b) forconfiguring a respective function of the second device, including, inaccordance with a determination that the first account (e.g., theaccount associated with the first device) was selected to be associatedwith the second device (and the second account was not selected to beassociated with the second device), displaying (1008), via the displaydevice, one or more selectable options (e.g., 942 a, 945 a, 947 a, 955a, 957 a, 959 a) associated with configuring the respective function ofthe second device without explicitly identifying a user account (e.g.,the second account) associated with the second device (e.g., withoutdisplaying 941), and in accordance with a determination that a secondaccount (e.g., a user account, not corresponding to the user of thefirst device), different from the first account, was selected to beassociated with the second device (and the first account was notselected to be associated with the second device), displaying (1010),via the display device, the one or more selectable options (e.g., 942 a,945 a, 947 a, 955 a, 957 a, 959 a) associated with configuring therespective function of the second device concurrently with an identifier(e.g. 941) that explicitly identifies the second account (e.g.,displaying a name of the user corresponding to the second account,displaying an email address corresponding to the second account).

In some embodiments, the first account is an existing user account. Insome embodiments, the first account is a user account in which the firstdevice (e.g., 900) is logged into during the setup process. In someembodiments, the second user account is a user account to be created. Insome embodiments, the second account is a user account in which thefirst device is not logged into during the setup process.

Explicitly identifying, at an first device, the user account for whichan second device is being configured for another user instead of a userof the first device provides the user with visual feedback aboutconfiguration settings that will be used to configure the second device.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in accordance with the determination that the firstaccount (e.g., the account associated with the first device (e.g., 900))was selected to be associated with the second device (e.g., 600), thefirst device initiates a process (e.g., display of user interfaces) forconfiguring the second device for the first account. In someembodiments, the process for configuring the second device for the firstaccount includes enabling a first set of features on the second devicerequiring communication between the first device and the second device(e.g., such that the first device transmits information to the seconddevice to enable the first set of features on the second device, sharingof a first set of features between the second device and the firstdevice). In some embodiments, in accordance with the determination thatthe second account (different from the first account) was selected to beassociated with the second device, the first device initiates a process(e.g., display of user interfaces) for configuring the second device forthe second account. In some embodiments, the process for configuring thesecond device for the second account does not include enabling the firstset of features on the second device that require communication betweenthe first device and the second device.

In some embodiments, the first set of features includes one or more of:sharing of physical activity data (e.g., corresponding to 948) (e.g.,data collected based on movement (or lack of movement) of the seconddevice and the first device that is indicative of physical activity ofthe corresponding user), automatic unlocking of devices (e.g., of thesecond device, of the first device) (e.g., based on, for example,proximity of the second device to the first device), sharing of locationdata (e.g., of the second device, of the first device, coordination ofnotifications/alerts (e.g., automatically dismissing a notification onone device (e.g., first device) when input has been received at theother device (e.g., the second device) to dismiss a correspondingnotification, automatically silencing an audio alert at one device(e.g., the first device) when input is received at the other device(e.g., the second device) to silence a corresponding alert beingprovided at the other device), handoff of application tasks (e.g.,displaying an indication on the display of one device (e.g., the firstdevice) based on a currently active (e.g., currently displayed)application of the other device (e.g., the second device), cameracontrol tasks (e.g., controlling (such as accessing a viewfinder of,initiating an image capture of) the camera of one device (e.g., thefirst device) using the other device (e.g., second device)), applicationinstallations (e.g., automatically installing a first application on onedevice (e.g., the second device) in response to a user request (at theother device) to install a corresponding (e.g., same, different versionof) application on the other device (e.g., the first device),communication disabling features (e.g., automatically placing one device(e.g., the first device) into airplane mode (e.g., by disabling cellularcommunications) in response to a user request (received at the otherdevice) to place the other device (e.g., the second device) intoairplane mode)), and payment account configuration (e.g., providing anaffordance (or initiating a process) for configuring (e.g., for NFCpayments) a payment account onto one device (e.g., the second device) inresponse to user input (e.g., received at the other device) configuringthe payment account for use on the other device (e.g., the firstdevice).

Sharing the set of features between the first device and the seconddevice enables a user to access their information across multipledevices. Similarly, not sharing set of features between the first deviceand the second device enables different user to maintain their owninformation on the separate devices. Managing how feature sharing isconfigured enhances the operability of the devices and makes theiruser-device interfaces more efficient (e.g., by helping to provideappropriate information to the appropriate user based on the accountthat is configured on the device) which, additionally, reduces powerusage and improves battery life of the device by enabling the users touse the devices more quickly and efficiently.

In some embodiments, displaying the identifier that explicitlyidentifies the second account includes displaying a name (e.g., 941, afirst name, a last name, a first and last name) corresponding to thesecond account. In some embodiments, the name is concurrently displayedwith a function or feature being configured, such as “Voice Control forEmma,” to identify the function/feature being configured and the userfor which it is being configured. In some embodiments, when the seconddevice is being configured for the first account, the configuration forthe same function/feature does not identify the first account. Forexample, configuration user interface for the feature/function maydisplay “Voice Control Setup,” without concurrently displaying the namethat corresponds to the first account. In some embodiments, the one ormore selectable options are one or more selectable options (e.g., 945 a)for configuring voice assistant settings on the second device. In someembodiments, in accordance with the determination that the secondaccount was selected to be associated with the second device, the firstdevice displays, via the display device (e.g., during the setupprocess), a user interface for configuring voice assistant settings onthe second device. In some embodiments, the one or more selectableoptions are displayed as part of the user interface for configuringvoice assistant settings, including a first voice assistant option toenable a voice assistant for use on the second device and a second voiceassistant option to not enable voice assistant for use on the seconddevice.

Explicitly identifying, at a first device, the user account for anotheruser instead of a user of the first device for which a second device isbeing configured provides the user of the first device with visualfeedback about configuration settings that will be used to configure thesecond device. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, during the setup process, in accordance with thedetermination that the first account (e.g., the account associated withthe first device) was selected to be associated with the second device,the first device displays, via the display device, a first prompt (e.g.,912 b in FIG. 9B) instructing for the second device to be worn (e.g., bythe user of the first device) and a second prompt (e.g., 912 a in FIG.9B) instructing for the second device (e.g., a display of the seconddevice) to be placed within a field of view of a camera sensor of thefirst device (e.g., displayed subsequent to (and optionally notcurrently with) displaying the prompt instruction for the second deviceto be worn, displayed subsequent to receiving information indicatingthat the second device is worn). In some embodiments, the first deviceoptionally monitors for information from the second device indicatingthat the second device is currently being worn before proceeding withdisplay of additional prompts. In some embodiments, during the setupprocess, in accordance with the determination that the second accountwas selected to be associated with the second device, the first devicedisplays, via the display device, a third prompt (e.g., the same as thesecond prompt, different from the second prompt) instructing for thesecond device (e.g., a display of the second device) to be placed withina field of view of a camera sensor of the first device withoutdisplaying a prompt (e.g., the first prompt) instructing for the seconddevice to be worn.

By not prompting the user to wear the second device in certaincircumstances, the device helps to avoid having the user wear the seconddevice when the device is not being set up for the user. This improvedfeedback to the user helps to avoid the user to avoid performing anunnecessary (or unhelpful) task, which may not be helpful for proceedingto the next stage of the device setup. In contrast, prompting (undercertain circumstances) the user to wear the second device provides theuser with tasks to perform to proceed to the next stage of device setup.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device (e.g., 900) displays, via thedisplay device, (e.g., during the setup process) one or more detailsabout data (e.g., application data, media (photos, videos, audio),documents, address book contacts) to be transmitted (e.g., from thefirst device, from a server using credentials (e.g., login/password) ofthe first account) to the second device (and, optionally, aboutconfigurations to be performed of the second device). In someembodiments, during the setup process, in accordance with thedetermination that the first account (e.g., the account associated withthe first device) was selected to be associated with the second device,the first device forgoes displaying, via the display device, the one ormore details about the data (e.g., application data, media (photos,videos, audio), documents, address book contacts) to be transmitted(e.g., from the first device, from a server using credentials (e.g.,login/password) of the first account) to the second device. In someembodiments, in accordance with the determination that the secondaccount was selected to be associated with the second device, the firstdevice displays information to inform the user that the second device isbeing configured for someone other than a user corresponding to thefirst account. In some embodiments, in accordance with the determinationthat the second account was selected to be associated with the seconddevice, the first device optionally informs (e.g., by displaying) theuser that the setup process will include opportunities to transfercontent (e.g., application data, media (photos, videos, audio),documents, address book contacts) to the second device. In someembodiments, in accordance with the determination that the secondaccount was selected to be associated with the second device, the firstdevice optionally informs (e.g., by displaying) the user that the setupprocess will include opportunities to configure the second device foroperating in a restricted mode, such as described above with respect toFIGS. 6A-6AC, FIG. 7, and FIG. 8, above.

Displaying one or more details about data to be transmitted provides theuser with visual feedback about the data that will be shared with thesecond device. This provides, for example, the user with an opportunityto decline the transmission of the information, thereby preventingunintended data from being shared with the second device. Providingimproved visual feedback to the user enhances the security of the deviceand the operability of the device, making the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 936) fortransmitting network settings (e.g., from the first device) to thesecond device. In some embodiments, the one or more selectable optionsare displayed as part of the user interface for transmitting networksettings. In some embodiments, the one or more selectable optionsinclude a first network configuration option (e.g., 937 a) to transmitnetwork configuration data (e.g., network name, network credentials(e.g., password)) for a first network (e.g., a wireless network, awireless local area network (wlan)) that is associated with a currentlocation of the first device (e.g., a first network that is currentlybeing accessed by the first device). In some embodiments, the firstnetwork configuration data is transmitted to the second device withouttransmitting network configuration data for a second network (e.g., asecond wireless network, a second wlan network) that is not currentlybeing accessed by the first device (e.g., only sharing networkconfiguration data for one network, even though the device has shareablenetwork configuration data for multiple networks).

In some embodiments, the user interface (e.g., 936) for transmittingnetwork settings (e.g., from the first device) to the second devicefurther includes a second network configuration option (e.g., 937 b) totransmit network configuration data (e.g., network name, networkcredentials (e.g., password)) for a plurality of networks. In someembodiments, the plurality of networks includes the first network andthe second network. In some embodiments, during the setup process, whiledisplaying the user interface for transmitting network settings, thefirst device detects a second user input. In some embodiments, duringthe setup process, in accordance with a determination that the seconduser input corresponds to activation of the first network configurationoption, the first device transmits, to the second device, networkconfiguration data (e.g., network name, network credentials (e.g.,password)) for the first network without transmitting networkconfiguration data for the second network. In some embodiments, duringthe setup process, in accordance with a determination that the seconduser input corresponds to activation of the second network configurationoption, the first device transmits, to the second device, networkconfiguration data (e.g., network name, network credentials (e.g.,password)) for the plurality of networks.

In some embodiments, the second user input indicates authorization totransfer the corresponding network configuration data one time (e.g., asingle-time transfer, not to transfer network configuration datarepeatedly for the same network, not to provide network configurationdata for future networks configured on the first device).

In some embodiments, the one or more selectable options include a thirdnetwork configuration option to not transmit network configuration data(e.g., network name, network credentials (e.g., password)) for the firstnetwork (e.g., a wireless network, a wlan network) and to not transmitnetwork configuration data (e.g., network name, network credentials(e.g., password)) for the second network (e.g., to not transmit networkconfiguration data for any network (any wifi network)). In someembodiments, in accordance with a determination that the second userinput corresponds to activation of the third network configurationoption: the first device forgoes transmitting, to the second device,network configuration data (e.g., network name, network credentials(e.g., password)) for the first network.

In some embodiments, the first device prompts the user to select fromamong sharing the current network's settings or sharing multiplenetworks' settings. In some embodiments, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface for transmittingnetwork settings (e.g., from the first device) to the second device. Insome embodiments, displaying the user displaying interface fortransmitting network settings includes displaying a first networkconfiguration option to transmit network configuration data (e.g.,network name, network credentials (e.g., password)) for a first network(e.g., a wireless network, a wlan network) that is currently beingaccessed by the first device and a second network configuration optionto transmit network configuration data (e.g., network name, networkcredentials (e.g., password)) for the first network (e.g., a wirelessnetwork, a wlan network) that is currently being accessed by the firstdevice and a second network (e.g., a second wireless network differentfrom the first network) that is not currently being accessed by thefirst device. In some embodiments, while displaying the user interfacefor transmitting network settings, the first device detects a seconduser input. In some embodiments, in accordance with a determination thatthe second user input corresponds to activation of the first networkconfiguration option, the first device transmits, to the second device,network configuration data (e.g., network name, network credentials(e.g., password)) for the first network without transmitting networkconfiguration data for the second network. In some embodiments, inaccordance with a determination that the second user input correspondsto activation of the second network configuration option, the firstdevice transmits, to the second device, network configuration data(e.g., network name, network credentials (e.g., password)) for the firstnetwork and the second network. In some embodiments, the second userinput indicates authorization to transfer the corresponding networkconfiguration data one time (e.g., a single-time transfer, not totransfer network configuration data repeatedly for the same network, notto provide network configuration data for future networks configured onthe first device).

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 964, 966) fortransmitting media (e.g., from the first device) to the second device.In some embodiments, displaying the user interface for transmittingmedia to the second device includes displaying a first representation(e.g., 967 a-967 g) of a first media (e.g., a photo, an album of photos,a video, audio), wherein the first media is stored on the first device asecond representation (e.g., 967 a-967 g) of a second media (e.g., aphoto, an album of photos, a video, audio). In some embodiments, thesecond media is associated with an account that is associated with thefirst device (and, optionally, stored on the first device). In someembodiments, the first device detects a first set of one or more userinputs. In some embodiments, in accordance with a determination that thefirst set of one or more user inputs correspond to a request to transmitthe first media without transmitting the second media, the first devicetransmits, to the second device, the first media without transmittingthe second media.

In some embodiments, the first set of one or more user inputs includesauthorization to transfer the corresponding media one time (e.g., asingle-time transfer, not to repeatedly transfer the selected media orto transfer other (non-selected) media, not to transfer additional mediain the future to the second device without first receiving userauthorization). In some embodiments, the first set of one or more userinputs includes authorization to share a collection of media with thesecond device where the media that is shared changes if the collectionof media changes (e.g., by the user of the first device adding to ordeleting from the collection of media).

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 976) forrequesting management access of a set of contactable users associatedwith a user of the second device. In some embodiments, displaying theuser interface for requesting management access of a set of contactableusers associated with a user of the second device includes displaying anoption to transmit a request (e.g., to the second device) to provide thefirst account access to manage the set of contactable users associatedwith the user of the second device (e.g., an address book stored on thesecond device, an address book stored at a server; an address bookincluding details for contactable users) of the second account. In someembodiments, during the setup process, in accordance with thedetermination that the first account (e.g., the account associated withthe first device) was selected to be associated with the second device,the first device forgoes displaying, via the display device (e.g.,during the setup process), the user interface for requesting managementaccess of the set of contactable users associated with the user of thesecond device.

In some embodiments, subsequent to receiving the request to provide thefirst account access to manage the address book, the second deviceprompts for approval to provide the first account access to manage theaddress book. In response to receiving approval to provide the firstaccount access to manage the address book, a predetermined time periodis initiated during which the first account does not have access tomanage (e.g., view contents of, modify contents of) the address book andafter (after the predetermined time period) which the first account doeshave access to manage (e.g., view contents of, modify contents of) theaddress book.

Prompting the user with an option to transmit a request to provideaccess to manage an address book of the second device provides atechnique by with the first user can modify address book entries of thesecond user, thereby reducing the need for the second user to configurethe address book and providing the first device with access to moreaddress book information. Providing the first device with access toadditional address book information enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 982) fortransmitting a set of contactable users associated with the user of thefirst device (e.g., address book contents, from the first device) to thesecond device. In some embodiments, displaying the user interface fortransmitting a set of contactable users associated with the user of thefirst device to the second device includes displaying a firstrepresentation (e.g., 983 a-983 h) (e.g., a name, a visualrepresentation, such as a photo) of first contactable user informationof a first contactable user (e.g., an address book entry for a firstentity) and a second representation (e.g., 983 a-983 h) (e.g., a name, avisual representation, such as a photo) of second contactable userinformation of a second contactable user (e.g., an address book entryfor a second entity). In some embodiments, the first contactable userinformation is stored on the first device. In some embodiments, thesecond contactable user information is stored on the first device. Insome embodiments, during the setup process, the first device detects asecond set of one or more user inputs. In some embodiments, during thesetup process, in accordance with a determination that the second set ofone or more user inputs correspond to a request to transmit the firstcontactable user information without transmitting the second contactableuser information, the first device transmits, to the second device, thefirst contactable user information without transmitting the secondcontactable user information.

In some embodiments, in response to detecting the second set of userinputs and in accordance with a determination that the second set of oneor more user inputs correspond to a request to transmit the firstcontactable user information and the second contactable userinformation, the first device transmits, to the second device, the firstcontactable user information and the second contactable userinformation. In some embodiments, the set of one or more user inputsincludes authorization to transfer the corresponding media one time(e.g., a single-time transfer, not to repeatedly transfer the selectedmedia or to transfer other (non-selected) media, not to transferadditional media in the future to the second device without firstreceiving user authorization). In some embodiments, transmitting thecontact information occurs without coordinate the first device and thesecond device to synchronize other entries in the address book. Thus,the transfer is optionally a one-time transfer of contact informationand future transfers of contact information would require userauthorization.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 986) forconfiguring the second device for a restricted mode (e.g., includingdisplaying options for configuring a schedule (e.g., days, times, hours,during school hours) during which to place the second device in therestricted mode. In some embodiments, during the setup process, thefirst device receives a third set of one or more inputs to configure theschedule during which to place the second device in the restricted mode.In some embodiments, during the setup process, in response to receivingthe third set of one or more inputs, the first device transmits (e.g.,to the second device) the schedule.

In some embodiments, while the second device is in the restricted mode,the second device provides limited functionality or information (e.g.,time and date), while restricting other functions, thereby allowing auser of the second device to maintain focus on a current task. Therestricted mode is described in further detail above with respect toFIGS. 6A-6AC, FIG. 7, and FIG. 8, above.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a security user interface (e.g., 930a, 930 b) for configuring security (e.g., passcode) for the seconddevice. In some embodiments, displaying the security user interfaceincludes: in accordance with a determination that an age of the usercorresponding to the second account is less than a (non-zero) thresholdage, displaying a prompt (e.g., 931 a) instructing for the usercorresponding to the first account to enter (e.g., at the first device,at the second device) a security input (e.g., a password, a passcode) tosecure the second device and to be subsequently used for unlocking thesecond device; and in accordance with a determination that the age ofthe user corresponding to the second account is greater than (or equalto) the (non-zero) threshold age, displaying a prompt (e.g., 931 b)instructing for (e.g., instructing for the first device to be handed tothe user corresponding the second account) the user corresponding to thesecond account to enter (e.g., at the first device, at the seconddevice) a security input (e.g., a password, a passcode, biometricinformation) to secure the second device and to be subsequently used forunlocked the second device.

In some embodiments, prior to detecting the first user input selectingthe respective account to be associated with the second device, thefirst device displays, via the display device (e.g., during the setupprocess), an account selection user interface (e.g., 918, 922 a, 922 b)for selecting the respective account to be associated with the seconddevice. In some embodiments, the account selection user interfaceincludes a first account option (e.g., 920 b) to create a new account(e.g., creating the second account) to be associated with the seconddevice and a second account option (e.g., 920 a, 923 a-923 c) to receiveinput identifying an existing account (e.g., identifying the secondaccount that already exists) to be associated with the second device. Insome embodiments, prior to detecting the first user input selecting therespective account to be associated with the second device, the firstdevice receives a third user input. In some embodiments, prior todetecting the first user input selecting the respective account to beassociated with the second device, in accordance with a determinationthat the third user input corresponds to activation of the first accountoption, the first device displays an account creation user interfaceconfigured to receive account information (e.g., email address, name,password) to create the second account. In some embodiments, prior todetecting the first user input selecting the respective account to beassociated with the second device, in accordance with a determinationthat the third user input corresponds to activation of the secondaccount option, the first device displays an account selection userinterface that includes identifiers for one or more existing accountscorresponding to a grouping of accounts (e.g., accounts linked togethersuch as accounts identified as corresponding to members of a family thatincludes the first user account), wherein the identifiers for the one ormore existing accounts includes an identifier (e.g., the name of theuser corresponding to the second account, an email address correspondingto the second account, a login corresponding to the second account) forthe second account, and wherein the first account is a member of thegrouping of accounts (e.g., the first account is linked to the one ormore existing accounts as their corresponding users being in the samefamily).

Displaying an account selection user interface that includes identifiersfor the one or more existing accounts corresponding to the grouping ofaccounts provides the user with ability to efficiently select from amonga list of likely accounts to use for setting up the second device. As aresult, the device avoids the need for the user to provide variousextraneous inputs to otherwise identify the account that should be usedfor setting up the second device. Reducing the number of inputs requiredto select an account enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, account selection user interface does not includean identifier for the first account. In some embodiments, the accountselection user interface includes an option for creating a new accountto be configured as part of the grouping of accounts (e.g., accountwould be created and linked to the one or more existing accounts).

In some embodiments, during the setup process, in accordance with adetermination that the second account was selected to be associated withthe second device and that the second account is not currentlyconfigured on a different device (e.g., other than the second device) ofa first type (e.g., of a type that is compatible with linking to thesecond device, a smartphone of a particular model or models), the firstdevice proceeds with the setup process for setting up the second deviceusing the first device (e.g., proceeding to displaying user interfacesfor/and transmitting: address book contacts, media, and network settingsto the second device). In some embodiments, during the setup process, inaccordance with a determination that the second account was selected tobe associated with the second device and that the second account iscurrently configured on a different device (e.g., other than the seconddevice) of the first type (e.g., of a type that is compatible withlinking to the second device, a smartphone of a particular model ormodels), the first device displays, via the display device, a prompt(e.g., as shown on 932) instructing for the second device to be set upusing the different device without proceeding with the setup process forsetting up the second device using the first device (e.g., withoutproceeding to display user interfaces for/and transmitting: address bookcontacts, media, and network settings to the second device). In someembodiments, the first device returns to the setup process after thefirst device detects an input (e.g., 934) corresponding to a request tocontinue while the prompt is displayed.

In some embodiments, during the setup process, in accordance with thedetermination that the second account was selected to be associated withthe second device, the first device displays, via the display device(e.g., during the setup process), a user interface (e.g., 964, 966) forselecting a media collection for synchronization (e.g., between thefirst device and the second device) with the second device. In someembodiments, displaying the user interface for selecting a mediacollection for synchronization (e.g., between the first device and thesecond device) with the second device includes displaying arepresentation of a media collection (e.g., 967 a-967 g) (e.g., acollection of media items, an album of photos and/or videos). In someembodiments, the first media collection is associated with a user of thefirst device (e.g., stored on the first device, stored on an externalserver using an account of the user of the first device). In someembodiments, the user interface for selecting a media collection forsynchronization also includes a second representation of a second mediacollection. In some embodiments, the second media is stored on the firstdevice. In some embodiments, during the setup process, the first devicedetects selection of the representation of the media collection. In someembodiments, during the setup process, subsequent to (e.g., in responseto) detecting selection of the representation of the media collection,the first device configures the media collection to be synchronized witha corresponding media collection of the second device. In someembodiments, photos and other media items in the media collection willbe available at the second device. In some embodiments, in the future,while the synchronization of the media collection is maintained, mediaitems added to the media collection will become available at the seconddevice and media items removed from the media collection will cease tobe available at the second device.

Note that details of the processes described above with respect tomethod 1000 (e.g., FIG. 10) are also applicable in an analogous mannerto the methods described above. For example, methods 700 and 800optionally includes one or more of the characteristics of the variousmethods described above with reference to method 1000. For example, thesecond device being configured in method 1000 is electronic device 600in methods 700 and 800. Thus, the first device (e.g., 900) can configureelectronic device 600 (e.g., the second device) to enter a restrictedmode during certain times (as configured at user interface 988 of FIG.9AG). Techniques related to the restricted mode are further describedwith respect to FIGS. 6A-6AC and methods 700 and 800. For brevity, thesedetails are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to reportelectronic devices exiting a restricted mode of operation. The presentdisclosure contemplates that in some instances, this gathered data mayinclude personal information data that uniquely identifies or can beused to contact or locate a specific person. Such personal informationdata can include demographic data, location-based data, telephonenumbers, email addresses, twitter IDs, home addresses, data or recordsrelating to a user's health or level of fitness (e.g., vital signsmeasurements, medication information, exercise information), date ofbirth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide more details regarding an electronic device exiting a restrictedmode. Accordingly, use of such personal information data enables usersto control a restricted mode associated with a user or an electronicdevice. Further, other uses for personal information data that benefitthe user are also contemplated by the present disclosure. For instance,health and fitness data may be used to provide insights into a user'sgeneral wellness, or may be used as positive feedback to individualsusing technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof devices operating according to a restricted mode, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. In anotherexample, users can select not to provide certain data related to exitinga restricted mode of an electronic device. In yet another example, userscan select to limit the length of time data is maintained. In additionto providing “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, reports of anelectronic device exiting a restricted mode can be based on non-personalinformation data or a bare minimum amount of personal information, suchas the content being requested by the device associated with a user,other non-personal information available to the service producing thereport, or publicly available information.

What is claimed is:
 1. A method comprising: at an electronic device witha display device: displaying, via the display device, a first userinterface of a respective type of user interface of the electronicdevice, wherein the first user interface of a respective type of userinterface includes one or more elements in a first arrangement;detecting a sequence of one or more inputs corresponding to a request tochange the current user interface of a respective type of user interfaceof the electronic device; in response to detecting the sequence of oneor more inputs corresponding to the request to change the current userinterface of a respective type of user interface of the electronicdevice, displaying, via the display device, a second user interface ofthe respective type of user interface as the current user interface of arespective type of user interface of the electronic device, wherein thesecond user interface of a respective type of user interface includesone or more elements that are different from the one or more elements ofthe first user interface of a respective type of user interface and/orare in a different arrangement than the first arrangement of the one ormore elements of the first user interface of a respective type of userinterface; after changing the current user interface of a respectivetype of user interface of the electronic device to the second userinterface of a respective type of user interface, detecting theoccurrence of a condition that corresponds to a trigger for displayingthe current user interface of a respective type of user interface of theelectronic device; and in response to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current timecorresponds to a predefined time range, displaying, via the displaydevice, a third user interface of a respective type of user interfacedifferent from the first user interface of a respective type of userinterface and the second user interface of a respective type of userinterface, wherein the third user interface of a respective type of userinterface includes a predefined set of elements different from the oneor more elements of the first user interface of a respective type ofuser interface and the one or more elements of the second user interfaceof a respective type of user interface, and wherein the predefined setof elements cannot be changed in response to input detected at theelectronic device; and in accordance with a determination that a currenttime does not correspond to the predefined time range, displaying thesecond user interface of a respective type of user interface.
 2. Themethod of claim 1, wherein the respective type of user interface is awatch face.
 3. The method of claim 2, further comprising: detecting asecond sequence of one or more inputs; and in response to detecting thesecond sequence of one or more inputs: in accordance with the secondsequence of one or more inputs being detected while displaying the firstuser interface of a respective type of user interface, performing anoperation; and in accordance with the second sequence of one or moreinputs being detected while displaying the third user interface of arespective type of user interface, foregoing performance of theoperation.
 4. The method of claim 1, wherein the predefined set ofelements includes the entire third user interface of a respective typeof user interface and additional elements cannot be added to the thirduser interface of a respective type of user interface.
 5. The method ofclaim 1, wherein the third user interface of a respective type of userinterface includes a distinguishing element, wherein the distinguishingelement is a visually distinguishable portion of the third userinterface of a respective type of user interface and the distinguishingelement is not included in the first user interface of a respective typeof user interface or the second user interface of a respective type ofuser interface.
 6. The method of claim 1, further comprising: whiledisplaying the second user interface of a respective type of userinterface, detecting a third sequence of one or more inputs; and inresponse to detecting the third sequence of one or more inputs whiledisplaying the second user interface of a respective type of userinterface, performing an operation; while displaying the third userinterface of a respective type of user interface, detecting the thirdsequence of one or more inputs; and in response to detecting the thirdsequence of one or more inputs while displaying the third user interfaceof a respective type of user interface, foregoing performance of theoperation.
 7. The method of claim 1, further comprising: prior todetecting the occurrence of the condition that corresponds to a triggerfor displaying the current user interface of a respective type of userinterface of the electronic device, displaying a first user interfacefor a first application, wherein displaying the third user interface ofa respective type of user interface includes ceasing to display thefirst user interface for the first application.
 8. The method of claim7, including after ceasing to display the first user interface for thefirst application, continuing to run the first application in thebackground.
 9. The method of claim 7, wherein displaying the third userinterface of a respective type of user interface includes: in accordancewith a determination that the first application is running in thebackground, displaying the third user interface of a respective type ofuser interface with a graphical element corresponding to the firstapplication; and in accordance with a determination that the firstapplication is not running, displaying the third user interface of arespective type of user interface without the graphical elementcorresponding to the first application.
 10. The method of claim 1,further comprising: while displaying the third user interface of arespective type of user interface, detecting a fourth sequence of one ormore inputs; and in response to detecting at least one of the inputs inthe fourth sequence of one or more inputs, displaying an exit userinterface with information for transition from a first mode, to a secondmode, wherein the second mode includes one or more functions notaccessible while in the first mode.
 11. The method of claim 10, whereinthe exit user interface includes a first portion that includes anaffordance for exiting the first mode, the method further comprising:receiving an input corresponding to selection of the affordance forexiting the first mode; and in response to detecting the inputcorresponding to selection of the affordance for exiting the first mode,displaying the second user interface of a respective type of userinterface.
 12. The method of claim 10, further comprising: whiledisplaying the exit user interface without displaying the first portionof the exit user interface that includes the affordance for exiting thefirst mode, detecting an input corresponding to a request to scroll theexit user interface; and in response to detecting the inputcorresponding to a request to scroll the user interface, scrolling theuser interface to display the first portion of the user interface thatincludes the affordance for exiting the first mode.
 13. The method ofclaim 10, wherein detecting the fourth sequence of one or more inputsincludes detecting a rotation of a rotatable input mechanism, the methodfurther comprising: in response to detecting the rotation of therotatable input mechanism, displaying the second user interface of arespective type of user interface.
 14. The method of claim 1, furthercomprising: while the current time corresponds to the predefined timerange and while the third user interface of a respective type of userinterface is not displayed, detecting that third user interface of arespective type of user interface redisplay criteria are met; and inresponse to detecting that the third user interface of a respective typeof user interface redisplay criteria are met, displaying the third userinterface of a respective type of user interface.
 15. The method ofclaim 1, further comprising: after displaying the third user interfaceof a respective type of user interface: detecting the occurrence of aninactivity condition; in response to detecting the occurrence of theinactivity condition, deactivating the display device; afterdeactivating the display device, detecting the occurrence of a conditionthat corresponds to a trigger for displaying a current user interface ofa respective type of user interface of the electronic device; inresponse to detecting the occurrence of a condition that corresponds toa trigger for displaying the current user interface of a respective typeof user interface of the electronic device: in accordance with adetermination that a current time corresponds to the predefined timerange, displaying the third user interface of a respective type of userinterface; and in accordance with a determination that a current timedoes not correspond to the predefined time range, displaying the seconduser interface of a respective type of user interface.
 16. The method ofclaim 1, wherein the third user interface of a respective type of userinterface includes an analog indication of time and a digital indicationof time.
 17. The method of claim 16, wherein an element of the analogindication of time corresponding to a current hour of the current timeis visually emphasized relative to elements of the analog indication oftime corresponding to hours other than the current hour.
 18. The methodof claim 1, further comprising: while the current time corresponds tothe predefined time range and while the electronic device is operatingin a first mode: detecting a fifth sequence of one or more inputs, thefifth sequence of one or more inputs including at least one input thatis detected while displaying the third user interface of a respectivetype of user interface; and in response to detecting the third sequenceof one or more inputs, exiting the first mode, wherein exiting the firstmode includes displaying the second user interface of a respective typeof user interface.
 19. The method of claim 1, wherein the second userinterface of a respective type of user interface includes a firstaffordance corresponding to an application, the method furthercomprising: while displaying the second user interface of a respectivetype of user interface, detecting an input corresponding to selection ofthe first affordance; and in response to detecting the inputcorresponding to selection of the first affordance, launching theapplication.
 20. The method of claim 1, wherein the predefined timerange is defined in accordance with a schedule that specifies differenttime ranges for different days of the week.
 21. The method of claim 1,while the current time does not correspond to the predefined time range:displaying, via the display device, a third user interface including anaffordance for activating a restricted mode; detecting an inputcorresponding to selection of the affordance for activating therestricted mode; and in response to detecting the input corresponding toselection of the affordance for activating the restricted mode,operating the electronic device in the restricted mode.
 22. The methodof claim 1, wherein the third user interface of a respective type ofuser interface includes an indication of a user's name and a digitalindication of time. 23-25. (canceled)
 26. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay device, the one or more programs including instructions for:displaying, via the display device, a first user interface of arespective type of user interface of the electronic device, wherein thefirst user interface of a respective type of user interface includes oneor more elements in a first arrangement; detecting a sequence of one ormore inputs corresponding to a request to change the current userinterface of a respective type of user interface of the electronicdevice; in response to detecting the sequence of one or more inputscorresponding to the request to change the current user interface of arespective type of user interface of the electronic device, displaying,via the display device, a second user interface of the respective typeof user interface as the current user interface of a respective type ofuser interface of the electronic device, wherein the second userinterface of a respective type of user interface includes one or moreelements that are different from the one or more elements of the firstuser interface of a respective type of user interface and/or are in adifferent arrangement than the first arrangement of the one or moreelements of the first user interface of a respective type of userinterface; after changing the current user interface of a respectivetype of user interface of the electronic device to the second userinterface of a respective type of user interface, detecting theoccurrence of a condition that corresponds to a trigger for displayingthe current user interface of a respective type of user interface of theelectronic device; and in response to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current timecorresponds to a predefined time range, displaying, via the displaydevice, a third user interface of a respective type of user interfacedifferent from the first user interface of a respective type of userinterface and the second user interface of a respective type of userinterface, wherein the third user interface of a respective type of userinterface includes a predefined set of elements different from the oneor more elements of the first user interface of a respective type ofuser interface and the one or more elements of the second user interfaceof a respective type of user interface, and wherein the predefined setof elements cannot be changed in response to input detected at theelectronic device; and in accordance with a determination that a currenttime does not correspond to the predefined time range, displaying thesecond user interface of a respective type of user interface.
 27. Anelectronic device, comprising: a display device; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying, via the display device, a first user interface of arespective type of user interface of the electronic device, wherein thefirst user interface of a respective type of user interface includes oneor more elements in a first arrangement; detecting a sequence of one ormore inputs corresponding to a request to change the current userinterface of a respective type of user interface of the electronicdevice; in response to detecting the sequence of one or more inputscorresponding to the request to change the current user interface of arespective type of user interface of the electronic device, displaying,via the display device, a second user interface of the respective typeof user interface as the current user interface of a respective type ofuser interface of the electronic device, wherein the second userinterface of a respective type of user interface includes one or moreelements that are different from the one or more elements of the firstuser interface of a respective type of user interface and/or are in adifferent arrangement than the first arrangement of the one or moreelements of the first user interface of a respective type of userinterface; after changing the current user interface of a respectivetype of user interface of the electronic device to the second userinterface of a respective type of user interface, detecting theoccurrence of a condition that corresponds to a trigger for displayingthe current user interface of a respective type of user interface of theelectronic device; and in response to detecting the occurrence of acondition that corresponds to a trigger for displaying the current userinterface of a respective type of user interface of the electronicdevice: in accordance with a determination that a current timecorresponds to a predefined time range, displaying, via the displaydevice, a third user interface of a respective type of user interfacedifferent from the first user interface of a respective type of userinterface and the second user interface of a respective type of userinterface, wherein the third user interface of a respective type of userinterface includes a predefined set of elements different from the oneor more elements of the first user interface of a respective type ofuser interface and the one or more elements of the second user interfaceof a respective type of user interface, and wherein the predefined setof elements cannot be changed in response to input detected at theelectronic device; and in accordance with a determination that a currenttime does not correspond to the predefined time range, displaying thesecond user interface of a respective type of user interface. 28-68.(canceled)